Re: [SOGo] SOGo 2.3.11 ngactivesocket problem

[Christian Mack]

Am 27.05.2016 um 14:41 schrieb Maxime RUBINO
(maxime.rub...@sfproduction.fr):
> Hi all,
> 
> i use nightly build of SOGo 2.3.11 and in my sogo.log i have strange
> errors :
> 
> May 27 14:37:10 sogod [25481]: [ERROR]
> <0x0x7fcda1794818[WOWatchDogChild]> FAILURE receiving status for child
> 14934
> May 27 14:37:10 sogod [25481]: [ERROR]
> <0x0x7fcda1794818[WOWatchDogChild]>   socket:
>  connectedTo=<0x0x7fcda1726e88[NGLocalSocketAddress]: /tmp/_ngsoc
> ket_25481_0x7fcda14d2f08_000> receive-timeout=1.000s>
> May 27 14:37:10 sogod [25481]: [ERROR]
> <0x0x7fcda1794818[WOWatchDogChild]>   exception:
> 
> NAME:NGSocketTimedOutException REASON:the socket was shutdown INFO:{errno =
>  11; error = "Resource temporarily unavailable"; stream = "{object =
>  connectedTo=<0x0x7fcda1726e88[NGLocalSocketAddress]:
> /tmp/_ngsocket_25481_0x7fcd
> a14d2f08_000> receive-timeout=1.000s>;}"; }
> May 27 14:37:10 sogod [25481]: <0x0x7fcda1794818[WOWatchDogChild]>
> sending terminate signal to pid 14934
> May 27 14:37:10 sogod [25481]: [ERROR]
> <0x0x7fcda1794818[WOWatchDogChild]> FAILURE notifying child 14934
> May 27 14:37:10 sogod [25481]: <0x0x7fcda1794818[WOWatchDogChild]>
> sending terminate signal to pid 14934
> 2016-05-27 14:37:10.097 sogod[14934] Forcing termination of EAS loop.
> 
> All services is OK, mysql/samba/sogo/... do you have an idea ?
> 

This means, that the SOGo watchdog can not talk to one of your SOGo workers.
That seems to be an ActiveSync one.
The watchdog will kill that worker, if it does not respond in time, in
order to prevent hanging processes.

Perhaps that is an initial sync with a big account via ActiveSync.
They can take some time and eat resources.
Check the corresponding settings in sogo.conf (and apache/nginx conf).


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature

[SOGo] SOGo 2.3.11 ngactivesocket problem

[Maxime RUBINO]

Hi all,

i use nightly build of SOGo 2.3.11 and in my sogo.log i have strange 
errors :


May 27 14:37:10 sogod [25481]: [ERROR] 
<0x0x7fcda1794818[WOWatchDogChild]> FAILURE receiving status for child 14934
May 27 14:37:10 sogod [25481]: [ERROR] 
<0x0x7fcda1794818[WOWatchDogChild]>   socket: 
 receive-timeout=1.000s>
May 27 14:37:10 sogod [25481]: [ERROR] 
<0x0x7fcda1794818[WOWatchDogChild]>   exception: 
 
NAME:NGSocketTimedOutException REASON:the socket was shutdown INFO:{errno =
 11; error = "Resource temporarily unavailable"; stream = "{object = 
 receive-timeout=1.000s>;}"; }
May 27 14:37:10 sogod [25481]: <0x0x7fcda1794818[WOWatchDogChild]> 
sending terminate signal to pid 14934
May 27 14:37:10 sogod [25481]: [ERROR] 
<0x0x7fcda1794818[WOWatchDogChild]> FAILURE notifying child 14934
May 27 14:37:10 sogod [25481]: <0x0x7fcda1794818[WOWatchDogChild]> 
sending terminate signal to pid 14934

2016-05-27 14:37:10.097 sogod[14934] Forcing termination of EAS loop.

All services is OK, mysql/samba/sogo/... do you have an idea ?

--
Cordialement,
Maxime RUBINO

--
users@sogo.nu
https://inverse.ca/sogo/lists