I found it myself. I added these lines in my SOGo conf:
SOGoMaximumPingInterval = 600;
SOGoMaximumSyncInterval = 600;
SOGoInternalSyncInterval = 30;
They were not present and the heartbeat timeout defaulted to 10 seconds.
Am Donnerstag, 27. August 2015 13:49 CEST, "Adrian" <[email protected]>
schrieb:
Hello all,
I am using SOGo as part of the iRedMail installation and I use an Android
handset with "nine" as an exchange client.
The problem is, that it consumes a lot of battery power, because it sends out
a lot of heartbeat requests to the SOGo server.
In the sogo.log I see something like this every 10 seconds:
Aug 27 13:45:46 sogod [15086]: <Android_IP> "POST /SOGo/Microsoft-Server-
ActiveSync?<some_random_characters>= HTTP/1.1" 200 19/328 10.448 - - 0
Aug 27 13:45:59 sogod [15086]: <Android_IP> "POST /SOGo/Microsoft-Server-
ActiveSync?<some_random_characters>=
= HTTP/1.1" 200 13/327 10.414 - - 0
The nine log shows something like:
08-27 13:37:04.355|I|Exchange|1|Ping end. Heartbeat out of bounds. old
duration 310 new duration 10
08-27 13:37:04.551|I|w|1|Ping start. items: HeartBeat=10
08-27 13:37:16.596|I|Exchange|1|Ping end. expired
So, it sets 10 seconds as a Heartbeat, tries to increase to 310 and fails. So
it goes back to 10 seconds.
Can I increase that heartbeat timeout somehow, so that "nine" does not fail
increasing the hearbeat?
Kind regards,
Adrian
--
[email protected]
https://inverse.ca/sogo/lists
--
[email protected]
https://inverse.ca/sogo/lists
