Hi qmail,

It could be that the processes are just busy with sync-requests in 
heartbeat-mode. 

They will be busy until the find changes in the folder(s) they are working on 
or after 3540.

 

Try to identify what they are doing. SOGoEASDebugEnabled = YES will help here.

What version of sogo are you using?

 

Regards,

Thomas

                                                                                
                                                                                
                                                                            

Von: users-requ...@sogo.nu [mailto:users-requ...@sogo.nu] Im Auftrag von 
qm...@top-consulting.net
Gesendet: Samstag, 2. April 2016 11:51
An: users@sogo.nu
Betreff: [SOGo] ActiveSync - too many processes

 

Hello,

 

I configured ActiveSync as per the online documentation and everything works 
fine as the sync goes but it seems that it spawns way too many sogod workers 
for just one EAS user.

 

It appears that everytime the mobile device ( Nexus 5, Android 6 ) sends a Sync 
request a new sogod process gets created. After a few minutes, the logs are 
full of these messages and the RAM keeps on increasing.

 

Apr 02 05:44:47 sogod [11530]: [WARN] <0x0x55d36157adb8[WOWatchDogChild]> pid 
11533 has been hanging in the same request for 6 minutes

Apr 02 05:44:55 sogod [11530]: [WARN] <0x0x55d36159cb18[WOWatchDogChild]> pid 
11541 has been hanging in the same request for 2 minutes

Apr 02 05:44:55 sogod [11530]: [WARN] <0x0x55d361590658[WOWatchDogChild]> pid 
11537 has been hanging in the same request for 5 minutes

Apr 02 05:45:09 sogod [11530]: [WARN] <0x0x55d3615a3c58[WOWatchDogChild]> pid 
11539 has been hanging in the same request for 7 minutes

Apr 02 05:45:25 sogod [11530]: [WARN] <0x0x55d36159bf28[WOWatchDogChild]> pid 
11540 has been hanging in the same request for 8 minutes

Apr 02 05:45:30 sogod [11530]: [WARN] <0x0x55d361590898[WOWatchDogChild]> pid 
11538 has been hanging in the same request for 2 minutes

Apr 02 05:45:33 sogod [11530]: [WARN] <0x0x55d361590418[WOWatchDogChild]> pid 
11536 has been hanging in the same request for 5 minutes

Apr 02 05:45:47 sogod [11530]: [WARN] <0x0x55d36157adb8[WOWatchDogChild]> pid 
11533 has been hanging in the same request for 7 minutes

Apr 02 05:45:55 sogod [11530]: [WARN] <0x0x55d36159cb18[WOWatchDogChild]> pid 
11541 has been hanging in the same request for 3 minutes

Apr 02 05:45:55 sogod [11530]: [WARN] <0x0x55d361590658[WOWatchDogChild]> pid 
11537 has been hanging in the same request for 6 minutes

Apr 02 05:46:09 sogod [11530]: [WARN] <0x0x55d3615a3c58[WOWatchDogChild]> pid 
11539 has been hanging in the same request for 8 minutes

 

This is the configuration in sogo.conf

 

  WOWorkersCount = 120;

  SOGoMaximumPingInterval = 3540;

  SOGoMaximumSyncInterval = 3540;

  SOGoInternalSyncInterval = 60;

  SOGoMaximumSyncWindowSize = 30;

  SOGoMaximumSyncResponseSize= 2048;

  WOWatchDogRequestTimeout=60;

  SxVMemLimit = 6100;

 

And Apache is setup like this:

 

ProxyPass /Microsoft-Server-ActiveSync 
http://192.168.1.92:20000/SOGo/Microsoft-Server-ActiveSync \

 retry=60 connectiontimeout=5 timeout=3600

 

We also spawn 10 sogod processes initially but eventually they all get consumed

 

 

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

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

Reply via email to