On 22/01/2015 10:38, lis...@outlook.de wrote:
Any ideas concerning the reason?
Have you tuned your proxy read timeouts in nginx? You had 90 seconds
from your previous post, which is way too low.
Have you also tuned:
SOGoMaximumPingInterval
SOGoMaximumSyncInterval
SOGoInternalSyncInterval
If not, a sogod process will not keep the EAS connection active for more
than 10 to 30 seconds - which will force your EAS device to re-establish
the connection, over and over.
If you increase these values, you must also increase your nginx/Apache
timeouts because they won't receive a response from sogod for X amount
of minutes.
If you do that, you must also adjust WOWatchDogRequestTimeout, because
by default, sogod processes aren't allowed to take more than 10 minutes
to handle a request.
--
Ludovic Marcotte
lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca
Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence
(http://packetfence.org)
--
users@sogo.nu
https://inverse.ca/sogo/lists
