Hi,
thanks for the feed back, but I tried already a lot of different settings
- no Sync size
- small Sync size (512)
- large Sync size (10240)
- short Watchdog timeout (6/10min)
- long watchdog timeout (1 hour)
and for all I got the same problem that processes are hanging in the same
request.
I was hoping for some new angles to attack that issue and perhaps somebody can tell
something from the log files and backtraces I provided?
Has somebody hints how to narrow down the possible root cause?
Additional debug output, ... - something more profound than fishing in the dark with
different settings?
Best regards
Florian
On 12.04.2016 13:06, Hubert Gilch (h...@sepag.de) wrote:
Hello Florian,
SOGoMaximumSyncWindowSize seems to be tricky: I had similar problems (SOGo V2.8) with
it. When set > 0, SOGo will use this value regardless what the client wants. Outlook
seems to request something small and when it more items than it requests the whole fetch
will be descarded and startet from the beginning.
For me it worked when SOGoMaximumSyncWindowSize is unset in the configuration file, then
SOGo respects what the client is requesting. Setting it to 0 should be the same, but
only when unset it worked in my case.
Mit freundlichem Gruß
i. A. Hubert Gilch
Systemadministrator
SEP Logistik AG
Am 12.04.2016 um 12:27 schrieb Florian Unger (florian.un...@intego.de):
With settings
SOGoMaximumSyncResponseSize = 10240;
SOGoMaximumSyncWindowSize = 256;
I still have the same issue.
Best regards
Florian
On 12.04.2016 11:11, Florian Unger (florian.un...@intego.de) wrote:
Hi,
all the topics I found on the net spoke about setting small values for sync to solve
issues so I tried these settings:
SOGoMaximumSyncResponseSize = 512;
SOGoMaximumSyncWindowSize = 256;
which did not not help.
I will try your configuration with a large response size and see if that is doing the
trick.
Thanks
Florian
On 11.04.2016 15:51, Christian Jensen (cmjscrip...@outlook.dk) wrote:
Hi.
have you tried setting 'SOGoMaximumSync****'
i had almost the same issue and after setting them Office 2013 synchronized
just fine.
SOGoMaximumSyncResponseSize = 10240;
SOGoMaximumSyncWindowSize = 256;
Regards
Christian
Den 11-04-2016 kl. 15:35 skrev Florian Unger (florian.un...@intego.de):
Hi,
I am having some trouble with a small scale SOGo installation (less than 10 users)
using SOGo 3.0.2 with ActiveSync and Outlook 2013 clients.
I have SOGo configured for 15 workers and these are the ActiveSync specific settings
I am using:
WOWorkersCount = 15;
SOGoMaximumPingInterval = 600;
SOGoMaximumSyncInterval = 600;
SOGoInternalSyncInterval = 30;
WOWatchDogRequestTimeout = 6;
SxVMemLimit = 768;
/* Debug */
SOGoEASDebugEnabled = YES;
After some time processes keep hanging in the same request until all workers are
occupied and I get error "[WOWatchDog]> No child available to handle incoming request!"
At the end is an example of the log file of process 6808 and the last requests it
got. I also made backtraces with gdb from that process (see attachment) - the
process was either in function NGDescriptorRecv or in a sleep from
SOGoActiveSyncDispatcher.
I tried increasing timeouts up to 1 hour as suggested in the Active Sync tuning
hints from the manual, but that did not help. Processes were sitting just longer
until they got killed by the watch dog.
Any hint how to resolve this issue would be great.
Best regards
Florian
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
