Hi, since 2.3.1 update we are getting repeated failure messages in SOGo log
Aug 04 09:20:03 sogod [2074]: [ERROR] <0x0x7fe6bedc6288[WOWatchDogChild]> FAILURE receiving status for child 4915 Aug 04 09:20:03 sogod [2074]: [ERROR] <0x0x7fe6bedc6288[WOWatchDogChild]> socket: <NGActiveSocket[0x0x7fe6bedd13d8]: mode=rw address=(null) connectedTo=<0x0x7fe6bedfcb48[NGLocalSocketAddress]: /tmp/_ngsocket_0x81a_0x7fe6bebf6b48_000> receive-timeout=1.000s> Aug 04 09:20:03 sogod [2074]: [ERROR] <0x0x7fe6bedc6288[WOWatchDogChild]> exception: <NGSocketTimedOutException: 0x7fe6bec7a1b8> NAME:NGSocketTimedOutException REASON:the socket was shutdown INFO:{errno = 11; error = "Resource temporarily unavailable"; stream = "{object = <NGActiveSocket[0x0x7fe6bedd13d8]: mode=rw address=(null) connectedTo=<0x0x7fe6bedfcb48[NGLocalSocketAddress]: /tmp/_ngsocket_0x81a_0x7fe6bebf6b48_000> receive-timeout=1.000s>;}"; } Aug 04 09:20:03 sogod [2074]: <0x0x7fe6bedc6288[WOWatchDogChild]> sending terminate signal to pid 4915 Aug 04 09:20:03 sogod [2074]: [ERROR] <0x0x7fe6bedc6288[WOWatchDogChild]> FAILURE notifying child 4915 Aug 04 09:20:03 sogod [2074]: <0x0x7fe6bedc6288[WOWatchDogChild]> sending terminate signal to pid 4915 Aug 04 09:20:05 sogod [2074]: <0x0x7fe6bedc6288[WOWatchDogChild]> child 4915 exited Aug 04 09:20:05 sogod [2074]: <0x0x7fe6bec175a8[WOWatchDog]> child spawned with pid 5385 Happens approximately every 5-10 minutes. Server load is minimal, number of http requests is negligible, system has enough free memory, there are like 15-30 active SOGo users, SOGo configuration is 6 workers, SxVMemLimit is default. Any idea what could be wrong? -- David Kmoch Technical University of Liberec Network management center Studentska 2, 461 17 Liberec tel: +420 485 353 633 -- users@sogo.nu https://inverse.ca/sogo/lists