View Issue Details

IDProjectCategoryView StatusLast Update
0003331SOGoBackend Calendarpublic2015-10-23 16:47
Reporterinfrasysteme Assigned Toludovic  
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionsuspended 
Platform[Server] LinuxOSDebianOS Version8 (Jessie)
Product Version2.3.1 
Summary0003331: sogod crash with an NGSocketTimedOutException exception
Description

Hi,

we have a problem with the sogod process. The process crash every 10 minutes.

the log is full of errors like this :

Sep 03 09:15:27 sogod [9347]: [ERROR] <0x0x7f48cbdfbcf0[WOWatchDogChild]> FAILURE receiving status for child 486
Sep 03 09:15:27 sogod [9347]: [ERROR] <0x0x7f48cbdfbcf0[WOWatchDogChild]> socket: <NGActiveSocket[0x0x7f48cbc592f0]: mode=rw address=(null) connectedTo=<0x0x7f48cbc702b0[NGLocalSocketAddress]: /tmp/_ngsocket_0x2483_0x7f48cba2bd30_000> receive-timeout=1.000s>
Sep 03 09:15:27 sogod [9347]: [ERROR] <0x0x7f48cbdfbcf0[WOWatchDogChild]> exception: <NGSocketConnectionResetException: 0x7f48cbca41d0> NAME:NGSocketConnectionResetException REASON:reached end of stream <NGActiveSocket[0x0x7f48cbc592f0]: mode=rw address=(null) connectedTo=<0x0
x7f48cbc702b0[NGLocalSocketAddress]: /tmp/_ngsocket_0x2483_0x7f48cba2bd30_000> receive-timeout=1.000s> INFO:{errno = 104; error = "Connection reset by peer"; stream = "{object = 0x7f48cbc592f0;}"; }
Sep 03 09:15:27 sogod [9347]: <0x0x7f48cbdfbcf0[WOWatchDogChild]> sending terminate signal to pid 486
Sep 03 09:15:27 sogod [9347]: [ERROR] <0x0x7f48cbdfbcf0[WOWatchDogChild]> FAILURE notifying child 486
Sep 03 09:15:27 sogod [9347]: <0x0x7f48cbdfbcf0[WOWatchDogChild]> sending terminate signal to pid 486
Sep 03 09:15:27 sogod [9347]: <0x0x7f48cbdfbcf0[WOWatchDogChild]> child 486 exited
Sep 03 09:15:27 sogod [9347]: <0x0x7f48cba50000[WOWatchDog]> child spawned with pid 3012
Sep 03 09:16:08 sogod [9347]: [ERROR] <0x0x7f48cbd2e3b0[WOWatchDogChild]> FAILURE receiving status for child 412
Sep 03 09:16:08 sogod [9347]: [ERROR] <0x0x7f48cbd2e3b0[WOWatchDogChild]> socket: <NGActiveSocket[0x0x7f48cbcb3f30]: mode=rw address=(null) connectedTo=<0x0x7f48cbd87120[NGLocalSocketAddress]: /tmp/_ngsocket_0x2483_0x7f48cba2bd30_000> receive-timeout=1.000s>
Sep 03 09:16:08 sogod [9347]: [ERROR] <0x0x7f48cbd2e3b0[WOWatchDogChild]> exception: <NGSocketTimedOutException: 0x7f48cbd0b1e0> NAME:NGSocketTimedOutException REASON:the socket was shutdown INFO:{errno = 11; error = "Resource temporarily unavailable"; stream = "{object = 0x7f
48cbcb3f30;}"; }
Sep 03 09:16:08 sogod [9347]: <0x0x7f48cbd2e3b0[WOWatchDogChild]> sending terminate signal to pid 412
Sep 03 09:16:08 sogod [9347]: [ERROR] <0x0x7f48cbd2e3b0[WOWatchDogChild]> FAILURE notifying child 412
Sep 03 09:16:08 sogod [9347]: <0x0x7f48cbd2e3b0[WOWatchDogChild]> sending terminate signal to pid 412
Sep 03 09:16:09 sogod [9347]: <0x0x7f48cbd2e3b0[WOWatchDogChild]> child 412 exited
Sep 03 09:16:09 sogod [9347]: <0x0x7f48cba50000[WOWatchDog]> child spawned with pid 3500
Sep 03 09:17:38 sogod [9347]: [ERROR] <0x0x7f48cbd24c10[WOWatchDogChild]> FAILURE receiving status for child 17872
Sep 03 09:17:38 sogod [9347]: [ERROR] <0x0x7f48cbd24c10[WOWatchDogChild]> socket: <NGActiveSocket[0x0x7f48cbe20f60]: mode=rw address=(null) connectedTo=<0x0x7f48cbca8ff0[NGLocalSocketAddress]: /tmp/_ngsocket_0x2483_0x7f48cba2bd30_000> receive-timeout=1.000s>
Sep 03 09:17:38 sogod [9347]: [ERROR] <0x0x7f48cbd24c10[WOWatchDogChild]> exception: <NGSocketTimedOutException: 0x7f48cbce1c20> NAME:NGSocketTimedOutException REASON:the socket was shutdown INFO:{errno = 11; error = "Resource temporarily unavailable"; stream = "{object = 0x7f
48cbe20f60;}"; }
Sep 03 09:17:38 sogod [9347]: <0x0x7f48cbd24c10[WOWatchDogChild]> sending terminate signal to pid 17872
Sep 03 09:17:38 sogod [9347]: [ERROR] <0x0x7f48cbd24c10[WOWatchDogChild]> FAILURE notifying child 17872
Sep 03 09:17:38 sogod [9347]: <0x0x7f48cbd24c10[WOWatchDogChild]> sending terminate signal to pid 17872
Sep 03 09:17:40 sogod [9347]: <0x0x7f48cbd24c10[WOWatchDogChild]> child 17872 exited
Sep 03 09:17:40 sogod [9347]: <0x0x7f48cba50000[WOWatchDog]> child spawned with pid 4660

Thanks for your help,

TagsNo tags attached.

Activities

Christian Mack

Christian Mack

2015-09-04 13:09

developer   ~0008891

Do you have ActiveSync enabled?

infrasysteme

infrasysteme

2015-09-08 08:37

reporter   ~0008894

Yes, ActiveSync is enabled.

Christian Mack

Christian Mack

2015-09-09 07:41

developer   ~0008895

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.

Also check that you have enough workers.
You need at least one worker for each ActiveSync connection.

ludovic

ludovic

2015-10-23 16:47

administrator   ~0009029

No feedback since suggestion provided.

Issue History

Date Modified Username Field Change
2015-09-03 09:45 infrasysteme New Issue
2015-09-04 13:09 Christian Mack Note Added: 0008891
2015-09-08 08:37 infrasysteme Note Added: 0008894
2015-09-09 07:41 Christian Mack Note Added: 0008895
2015-10-23 16:47 ludovic Note Added: 0009029
2015-10-23 16:47 ludovic Status new => resolved
2015-10-23 16:47 ludovic Resolution open => suspended
2015-10-23 16:47 ludovic Assigned To => ludovic