I have a longstanding installation of SOGo that was reasonably stable until recently. I stared experiencing intermittent instability such as:

 * Any UI action (e.g., select email message) would hang.
 * Login would succeed but I would be greeted with a blank screen.

I updated to 5.12.4 and did a bunch of changes (basically increased WOWorkersCount), but the application seems to be suffering from resource exhaustion.

I started seeing a bunch of:

sogod [217867]: [ERROR] <0x0x55980c462e60[WOWatchDog]> No child available to handle incoming request!

I edited /etc/default/sogo and changed PREFORK to 10, then to 20.

I changed /etc/memcached.conf and increased the memory ceiling from 64 MB to 512MB.

In htop, the memory usage is pegged at 5GB of 16GB total, so it does not seem to be server memory limitation.

Other log entries that may or may not be relevant:

sogod [301075]: [ERROR] <0x0x7f4346b543e0[GCSAdminFolder]> 'OCSAdminURL' is not set

    I edited sogo.conf and included this setting, so this is probably fixed by now

sogod [303128]: <0x55c1aa8257d0[SOGoMailAccount]:0> renewing imap4 password

    I see a bunch of these, not clear to me if this is an issue.

sogod [303126]: [WARN] <0x0x7ff7cc52ebe0[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder

sogod [303118]: [WARN] <0x0x55c1a9f7cbc0[WOWatchDogChild]> pid 303139 has been hanging in the same request for 1 minutes

    I see a lot of these warnings, and I imagine that they relate to No child available to handle incoming request!

If anyone has any troubleshooting suggestion, please let me know.

Thanks,

Andrei Goldchleger

Reply via email to