Christian,
I'm using mailcow dockerized.
When I change PREFORK, nothing happens... number of process is the same.
I changed WOWorkersCount to 100 and I have 101 proccess's
[root@mail ~]# ps -ef | grep -i sogo | wc -l
101
What's recommended workers to 280 mailboxes?
This is constantly down...
Regards,
Pedro Antunes
On 05/02/2019, 13:41, "[email protected] on behalf of Christian Mack"
<[email protected] on behalf of [email protected]> wrote:
Hello
This means, you do not have enough workers running.
Beware WOWorkersCount in sogo.conf only affects SOGo when running in
manual debug mode.
Check your default configuration used on startup.
On Debian/Ubuntu systems you will find it in /etc/default/sogo
Value PREFORK will set the amount of workers.
Kind regards,
Christian Mack
Am 05.02.19 um 13:04 schrieb Pedro Antunes ([email protected]):
> Hi again,
>
> I have constantly with bellow error:
>
> sogo-mailcow_1 | Feb 5 11:38:30 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:30 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:30 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
> sogo-mailcow_1 | Feb 5 11:38:32 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
>
> After that, I need restart sogo to solve this situation temporarily.
>
> At this moment I have this configuration:
> 280 mailboxes.
>
> WOWorkersCount = "40";
> SxVMemLimit = 384;
> SOGoMaximumPingInterval = 3540;
> SOGoInternalSyncInterval = 45;
> SOGoMaximumSyncInterval = 60;
>
> Regards,
>
> Pedro Antunes
>
>
> On 05/02/2019, 09:52, "Pedro Antunes" <[email protected]> wrote:
>
> Thank you for the clarification. __
>
>
> Regards,
> Pedro Antunes
>
> On 05/02/2019, 08:08, "[email protected] on behalf of Christian
Mack" <[email protected] on behalf of [email protected]> wrote:
>
> Hello
>
> You use ActiveSync.
> ActiveSync blocks one worker for long times.
> Those messages are normal then.
> So nothing to worry about, as long as you don't get:
>
> ... [WARN] <0x0x56316ad28f30[WOWatchDogChild]> safety belt --
sending
> KILL signal to pid 18838
>
> Only then is your worker killed, because it exceeded the set max
time in
> WOWatchDogRequestTimeout (in Minutes).
>
>
> Kind regards,
> Christian Mack
>
>
> Am 04.02.19 um 19:22 schrieb Pedro Antunes ([email protected]):
> > Hi All,
> >
> > I migrated my production server (today) to mailcow.
> >
> > After analyze logs, I view that I have these constantly WARNS.
> >
> > Anybody have this problem? How I can solve it?
> >
> >
> > sogo-mailcow_1 | Feb 4 18:15:31 05e81f192545 sogod [11]:
[WARN] <0x0x557253cc7640[WOWatchDogChild]> pid 455 has been hanging in the same
request for 6 minutes
> > sogo-mailcow_1 | Feb 4 18:15:31 05e81f192545 sogod [11]:
[WARN] <0x0x557253c672c0[WOWatchDogChild]> pid 52 has been hanging in the same
request for 8 minutes
> > sogo-mailcow_1 | Feb 4 18:15:41 05e81f192545 sogod [11]:
[WARN] <0x0x557253c5b1c0[WOWatchDogChild]> pid 448 has been hanging in the same
request for 13 minutes
> > sogo-mailcow_1 | Feb 4 18:15:41 05e81f192545 sogod [11]:
[WARN] <0x0x557253e0a630[WOWatchDogChild]> pid 72 has been hanging in the same
request for 13 minutes
> > sogo-mailcow_1 | Feb 4 18:15:42 05e81f192545 sogod [11]:
[WARN] <0x0x557253cc7290[WOWatchDogChild]> pid 451 has been hanging in the same
request for 13 minutes
> > sogo-mailcow_1 | Feb 4 18:15:42 05e81f192545 sogod [11]:
[WARN] <0x0x557253cce1b0[WOWatchDogChild]> pid 452 has been hanging in the same
request for 13 minutes
> > sogo-mailcow_1 | Feb 4 18:15:43 05e81f192545 sogod [11]:
[WARN] <0x0x557253c921e0[WOWatchDogChild]> pid 454 has been hanging in the same
request for 13 minutes
> > sogo-mailcow_1 | Feb 4 18:15:52 05e81f192545 sogod [11]:
[WARN] <0x0x557253cc6b00[WOWatchDogChild]> pid 380 has been hanging in the same
request for 3 minutes
> > sogo-mailcow_1 | Feb 4 18:15:53 05e81f192545 sogod [11]:
[WARN] <0x0x557253c5c6a0[WOWatchDogChild]> pid 49 has been hanging in the same
request for 7 minutes
> > sogo-mailcow_1 | Feb 4 18:15:57 05e81f192545 sogod [11]:
[WARN] <0x0x557253c67c20[WOWatchDogChild]> pid 530 has been hanging in the same
request for 3 minutes
> > sogo-mailcow_1 | Feb 4 18:16:00 05e81f192545 sogod [11]:
[WARN] <0x0x557253cc6e10[WOWatchDogChild]> pid 406 has been hanging in the same
request for 18 minutes
> > sogo-mailcow_1 | Feb 4 18:16:04 05e81f192545 sogod [11]:
[WARN] <0x0x557253caad30[WOWatchDogChild]> pid 66 has been hanging in the same
request for 9 minutes
> > sogo-mailcow_1 | Feb 4 18:16:05 05e81f192545 sogod [11]:
[WARN] <0x0x557253cac340[WOWatchDogChild]> pid 70 has been hanging in the same
request for 2 minutes
> > sogo-mailcow_1 | Feb 4 18:16:05 05e81f192545 sogod [11]:
[WARN] <0x0x557253c673e0[WOWatchDogChild]> pid 279 has been hanging in the same
request for 18 minutes
> > sogo-mailcow_1 | Feb 4 18:16:09 05e81f192545 sogod [11]:
[WARN] <0x0x557253c5d160[WOWatchDogChild]> pid 456 has been hanging in the same
request for 8 minutes
> > sogo-mailcow_1 | Feb 4 18:16:10 05e81f192545 sogod [11]:
[WARN] <0x0x557253cab720[WOWatchDogChild]> pid 69 has been hanging in the same
request for 17 minutes
> > sogo-mailcow_1 | Feb 4 18:16:12 05e81f192545 sogod [11]:
[WARN] <0x0x557253cc7010[WOWatchDogChild]> pid 81 has been hanging in the same
request for 8 minutes
> > sogo-mailcow_1 | Feb 4 18:16:12 05e81f192545 sogod [11]:
[WARN] <0x0x557253cc6ce0[WOWatchDogChild]> pid 78 has been hanging in the same
request for 8 minutes
> > sogo-mailcow_1 | Feb 4 18:16:12 05e81f192545 sogod [11]:
[WARN] <0x0x557253c5b670[WOWatchDogChild]> pid 47 has been hanging in the same
request for 8 minutes
> > sogo-mailcow_1 | Feb 4 18:16:12 05e81f192545 sogod [11]:
[WARN] <0x0x557253c5b9e0[WOWatchDogChild]> pid 48 has been hanging in the same
request for 8 minutes
> > sogo-mailcow_1 | Feb 4 18:16:12 05e81f192545 sogod [11]:
[WARN] <0x0x557253c5b0c0[WOWatchDogChild]> pid 273 has been hanging in the same
request for 8 minutes
> > sogo-mailcow_1 | Feb 4 18:16:13 05e81f192545 sogod [11]:
[WARN] <0x0x557253c5b2e0[WOWatchDogChild]> pid 450 has been hanging in the same
request for 4 minutes
> >
> > Regards,
> > Pedro Antunes
> >
>
--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416
--
[email protected]
https://inverse.ca/sogo/lists
