On Wed, Dec 14, 2022 at 9:34 AM admin <[email protected]> wrote: > Hello, we have a problem after we migrate sogo to new virtual server. > There is some logs. First error log: <0x0x564cf6fae340[WOWatchDog]> No > child available to handle incoming request! > Default/sogo log: > # The amount of processes that should be spawned (Default: 3) > PREFORK=85 > > # The name of the account under which SOGo will be running (Default: > sogo) > # USER=sogo > Sogo.config: > { > // > // - Official SOGo document: > http://sogo.nu/support/index.html#/documentation > // - Mailing list: http://sogo.nu/support/index.html#/community > // > > // Daemon address and port > WOPort = 127.0.0.1:20000; > > // PID file > //WOPidFile = /var/run/sogo/sogo.pid; > > // Log file > //WOLogFile = /var/log/sogo/sogo.log; > > // Enable verbose logging. Reference: > // > > http://www.sogo.nu/nc/support/faq/article/how-to-enable-more-verbose-logging-in-sogo.html > //SOGoDebugRequests = YES; > //SOGoEASDebugEnabled = YES; > //ImapDebugEnabled = YES; > //LDAPDebugEnabled = YES; > //MySQL4DebugEnabled = YES; > //PGDebugEnabled = YES; > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Enabling those debugging parameters and restarting sogod will help you diagnose the problem and fix it.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
