Re: [SSI-devel] 1.9 icssvr_nanny: spawn_daemon_procerror=-11, will be retried
Brought to you by:
brucewalker,
rogertsang
From: Roger T. <rog...@gm...> - 2005-08-23 02:49:42
|
Looks like the system was running out of inodes... These numbers are a bit suspicious. [root@node1 fs]# cat dentry-state 29050 16830 45 0 0 0 [root@node1 fs]# cat inode-state 25552 3007 0 0 0 0 0 [root@node1 fs]# cat inode-nr 25555 3007 On 8/22/05, Roger Tsang <rog...@gm...> wrote: > By the way kdb on the remote node never hit ssidev_remote_open(). I > can run commands on the local node, even open new tty's, but any > commands to the filesystem like `echo > xxx' or `ls` will not return. > Shortly after, I run out of resources on all nodes; can't fork new > processes. Also I don't see any immediate indications of memory > starvation. >=20 > -Roger >=20 >=20 > On 8/22/05, John Byrne <joh...@hp...> wrote: > > Roger Tsang wrote: > > > Just wait. I think this might be related to my rmtfb fix... > > > > > > Roger > > > > The newcli stuff maybe. I can produce the -11 without it. > > > > What happens is that the node 1 thinks the pty is on node 2 and node 2 > > thinks the pty is on node 1. ssidev_remote_open ping-pongs between both > > nodes until things break. Something isn't being cleaned up/initialized > > properly when the pty is reused on a different node. > > > > John > > > > > > > > > > On 8/22/05, John Byrne <joh...@hp...> wrote: > > > > > >>Roger Tsang wrote: > > >> > > >>>I just fixed the earlier problem.. hmm. > > >>> > > >> > > >>So, I'm a little confused at the moment, then. Is the "spawm_daemon" > > >>problem the only problem you currently have with ttys and rmtfbs? > > >> > > >>John > > >> > > > > > > > > > > > |