Just a guess, have you stopped sogo completely and checked if there are any zombie processes still laying around? if so kill them, then restart sogo.
On Thu, Oct 07, 2010 at 06:35:42PM +0530, Mohit Chawla wrote: > We are facing the same problem on one of our servers here on Debian after > upgrading to 1.3.2, anyone got a clue ? > > 2010/10/1 Anton Popov <a...@antt.org> > > > I get this every 20 minutes or so and then I have to kill sogo/apache > > to get the machine running again. > > Started last night for no apparent reason. > > > > > > > > Upgraded to latest nightly this morning - it's still happeneing. > > > > <0x0x1bd4c4d0[WOHttpTransaction]> client disconnected during delivery of > > response for <WORequest[0x0x1ddc3270]: method=GET uri=/SOGo app=SOGo > > rqKey=(nil) rqPath=(nil)> (len=0): the socket was shutdown > > 127.0.0.1 - - [01/Oct/2010:10:32:32 GMT] "GET /SOGo HTTP/1.1" 302 0/0 > > 0.990 - - 4K > > Oct 01 10:33:26 sogod: SOGo watchdog [6572]: [ERROR] > > <0x0x1b8b2380[WOWatchDogChild]> FAILURE receiving status for child 6573 > > Oct 01 10:33:31 sogod: SOGo watchdog [6572]: [ERROR] > > <0x0x1b8b2380[WOWatchDogChild]> socket: <NGActiveSocket[0x0x1b8b7350]: > > mode=rw address=(nil) connectedTo=<0x0x1b8b7e40[NGLocalSocketAddress]: > > /tmp/_ngsocket_0x19ac_0x1b7090d0_000> receive-timeout=1.000s> > > Oct 01 10:33:31 sogod: SOGo watchdog [6572]: > > <0x0x1b8b2380[WOWatchDogChild]> sending terminate signal to pid 6573 > > Oct 01 10:33:31 sogod: SOGo watchdog [6572]: [ERROR] > > <0x0x1b8b2380[WOWatchDogChild]> FAILURE notifying child 6573 > > Oct 01 10:33:31 sogod: SOGo watchdog [6572]: > > <0x0x1b8b2380[WOWatchDogChild]> sending terminate signal to pid 6573 > > Oct 01 10:33:33 sogod: SOGo watchdog [6572]: [ERROR] > > <0x0x1b8b2380[WOWatchDogChild]> FAILURE receiving status for child 6573 > > Oct 01 10:33:33 sogod: SOGo watchdog [6572]: [ERROR] > > <0x0x1b8b2380[WOWatchDogChild]> socket: <NGActiveSocket[0x0x1b8b7350]: > > mode=rw address=(nil) connectedTo=<0x0x1b8b7e40[NGLocalSocketAddress]: > > /tmp/_ngsocket_0x19ac_0x1b7090d0_000> receive-timeout=1.000s> > > Oct 01 10:33:33 sogod: SOGo watchdog [6572]: > > <0x0x1b8b2380[WOWatchDogChild]> sending terminate signal to pid 6573 > > Oct 01 10:33:33 sogod: SOGo watchdog [6572]: [ERROR] > > <0x0x1b8b2380[WOWatchDogChild]> FAILURE notifying child 6573 > > Oct 01 10:33:33 sogod: SOGo watchdog [6572]: > > <0x0x1b8b2380[WOWatchDogChild]> sending terminate signal to pid 6573 > > Oct 01 10:36:57 sogod: SOGo watchdog [6572]: > > <0x0x1b8b2380[WOWatchDogChild]> child 6573 exited > > Oct 01 10:36:57 sogod: SOGo watchdog [6572]: <0x0x1b87ae90[WOWatchDog]> > > child spawned with pid 7398 > > > > > > Anyone have any clue what might be wrong? > > > > > > Thanks, > > > > Anton. > > -- > > users@sogo.nu > > https://inverse.ca/sogo/lists > > > -- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
