Hi,

We are receiving a number of these errors in the sogo log. I found a post which matches this error and Developer Christian Mack responded as below. However, I do not know where to find the ActiveSync ProxyPass rule. Could someone direct me to its location or give some information on how to change it.

Thanks,

Oct 29 04:11:26 sogod [22017]: [ERROR] <0x0x55b68981c320[WOWatchDogChild]> FAILURE receiving status for child 20558
Oct 29 04:11:26 sogod [22017]: [ERROR] <0x0x55b68981c320[WOWatchDogChild]> socket: <NGActiveSocket[0x0x55b6897519f0]: mode=rw address=(null) connectedTo=<0x0x55b6897bd400[NGLocalSocketAddress]: /tmp/_ngsocket_22017_0x55b68944cf70_000> receive-timeout=5.000s>
Oct 29 04:11:26 sogod [22017]: [ERROR] <0x0x55b68981c320[WOWatchDogChild]> exception: <NGSocketTimedOutException: 0x55b6896e8f00> NAME:NGSocketTimedOutException REASON:the socket was shutdown INFO:{errno = 11; error = "Resource temporarily unavailable"; stream = "{object = 0x55b6897519f0;}"; }
Oct 29 04:11:26 sogod [22017]: <0x0x55b68981c320[WOWatchDogChild]> sending terminate signal to pid 20558
Oct 29 04:11:26 sogod [22017]: [ERROR] <0x0x55b68981c320[WOWatchDogChild]> FAILURE notifying child 20558
Oct 29 04:11:26 sogod [22017]: <0x0x55b68981c320[WOWatchDogChild]> sending terminate signal to pid 20558

Christian Mack Replied:
Looks for me, like your ActiveSync connection from your proxy apache to the SOGo worker is closed premature.
Please check your timeout setting in the ActiveSync ProxyPass rule.
Then increase your SOGo setting for WOWatchDogRequestTimeout matching this time.
ActiveSync connections can last up to 1 hour, depending on your ActiveSync settings.