Robin Lee Powell wrote: > I don't know that this is a vserver problem, but I can't find any > other source for it, so... > > I'm running mooix (a MUD) under vserver; uname for the outer host > says 2.6.17.8-vs2.0.2-rc29 Really old kernel, you should really consider upgrading. > At some point recently, idle connections to the MUD started getting > dropped for no apparent reason at all. It looks like certain > processes are getting SIGTERMed, and I can't figure out why. > > Any help here would be very appreciated. > > There's a process called "prompt", which polls a file for changes, > that is often the one TERMd; either that or the process listening on > the other end of a socket from "prompt". Here's some strace output > from "prompt" getting killed: > > 1192618964.154960 fstat64(9, {st_mode=S_IFREG|0660, st_size=0, ...}) = 0 > 1192618964.155046 select(9, [8], NULL, NULL, {0, 300000}) = 0 (Timeout) > 1192618964.454959 fstat64(9, {st_mode=S_IFREG|0660, st_size=0, ...}) = 0 > 1192618964.455046 select(9, [8], NULL, NULL, {0, 300000}) = 0 (Timeout) > 1192618964.782783 fstat64(9, {st_mode=S_IFREG|0660, st_size=0, ...}) = 0 > 1192618964.796336 select(9, [8], NULL, NULL, {0, 300000}) = 0 (Timeout) > 1192618965.094850 fstat64(9, {st_mode=S_IFREG|0660, st_size=0, ...}) = 0 > 1192618965.094936 select(9, [8], NULL, NULL, {0, 300000}) = 0 (Timeout) > 1192618965.394805 fstat64(9, {st_mode=S_IFREG|0660, st_size=0, ...}) = 0 > 1192618965.394890 select(9, [8], NULL, NULL, {0, 300000}) = ? ERESTARTNOHAND (To be restarted) > 1192618965.590008 --- SIGTERM (Terminated) @ 0 (0) --- > 1192618965.590136 ioctl(8, TCXONC, TCOON) = 0 > 1192618965.590192 rt_sigprocmask(SIG_BLOCK, [INT], [TERM], 8) = 0 > 1192618965.590252 ioctl(8, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon -echo ...}) = 0 > 1192618965.591181 +++ killed by SIGKILL +++ SIGKILL != SIGTERM. Check dmesg on the host, most likely that's the OOM-killer doing its thing to your process. -- Daniel Hokka Zakrisson