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:2;
// 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;
// Define the URL to online help for SOGo. When set, an additional
icon
// will appear near the logout button in SOGo's web interface. The
URL
// will always be open in a blank target.
//SOGoHelpURL = '';
// set the maximum allowed size for content being sent to SOGo, this
can
// also limit the file attachment size being uploaded to SOGo when
// composing a mail.
// The value is in kilobyte. Default is 0 or disabled (unlimit).
WOMaxUploadSize = 102400;
// Parameter used to set the maximum allowed email message size when
// composing a mail.
// The value is in kilobytes. By default, the value is 0, or
disabled so
// no limit will be set.
SOGoMaximumMessageSizeLimit = 102400;
// Performance Tuning
//
// The amount of instances of SOGo that will be spawned to handle
multiple
// requests simultaneously. When started from the init script, that
amount
// is overriden by the `PREFORK=` setting in /etc/sysconfig/sogo or
// /etc/default/sogo. A value of 3 is a reasonable default for low
usage.
// The maximum value depends on the CPU and IO power provided by
your
// machine: a value set too high will actually decrease performances
under
// high load.
//
// You should have at least one child per EAS device configured to
use
// "push". You must also have more children than you have EAS
devices
// configured to use "push" - in order to handle normal SOGo
requests to
// its Web or DAV interfaces.
//
// Defaults to 1 when unset, increase it if you see below error
message in
// sogo log file: 'No child available to handle incoming request'
//
// WARNING:
// - on RHEL/CentOS, this setting is controlled by parameter
//'PREFORK=' defined in /etc/sysconfig/sogo.
// - on Debian/Ubuntu, this setting is controlled by parameter
//'PREFORK=' defined in /etc/default/sogo.
WOWorkersCount =70;
// Parameter used to set the maximum amount of time, in seconds,
SOGo will
// wait before replying to a Ping command.
// If not set, it defaults to 10 seconds.
SOGoMaximumPingInterval = 3540;
// Parameter used to set the maximum amount of time, in seconds,
SOGo will
// wait before replying to a Sync command.
// If not set, it defaults to 30 seconds.
SOGoMaximumSyncInterval = 3540;
// Parameter used to set the maximum amount of time, in seconds,
SOGo will
// wait before doing an internal check for data changes (add,
delete, and
// update). This parameter must be lower than
SOGoMaximumSyncInterval and
// SOGoMaximumPingInterval.
// If not set, it defaults to 10 seconds.
SOGoInternalSyncInterval = 30;
// Specifies the number of minutes after which a busy child process
will be
// killed by the parent process.
// Defaults to 10 (minutes).
WOWatchDogRequestTimeout = 61;
// Overwrite the maximum number of items returned during a Sync
operation.
// Defaults to 0, which means no overwrite is performed.
// Setting this parameter to a value greater than 512 will have
unexpected
// behaviour with various ActiveSync clients.
//SOGoMaximumSyncWindowSize = 100;
// Overwrite the maximum response size during a Sync operation.
// The value is in kilobytes. Setting this to 512 means the response
size
// will be of 524288 bytes or less (or a bit greater if needed for
syncing
// one item). Note that if you set the value too low and a mail
message
// (or any other object like calendar events, tasks and contacts)
surpasses
// it, it will still be synced but only this item will be.
// Defaults to 0, which means no overwrite is performed.
//
// Say you have these five mails and you set the limit to 512KB:
// 1. 250 KB
// 2. 250 KB
// 3. 25 KB
// 4. 750 KB
