[horde] activesync debug log never stop filling up with this message

[Michael J Rubinsky]

Quoting Samuel Wolf <samuel at sheepflock.de>:

> Hi,
>
> is it normal that the activesync debug log never stop filling up  
> with this message every three seconds?
> Switch of the activesync device do not stop it, only way is restart  
> apache server.
> Start again after the first sync of the activesync device.
>
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing state for  
> collection: Sent, synckey: {xxx-xxx-xxx-xxx}7
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Loading state for synckey  
> {xxx-xxx-xxx-xxx}7
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing message diff  
> engine for Sent
> 2013-01-02T02:24:58+01:00 DEBUG: [12810]  
> Horde_Core_ActiveSync_Driver::getServerChanges(Sent, 1357089438,  
> 1357089898, 0, 1)
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Found 0 message changes in Sent.
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing state for  
> collection: INBOX, synckey: {xxx-xxx-xxx-xxx}5
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Loading state for synckey  
> {xxx-xxx-xxx-xxx}5
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing message diff  
> engine for INBOX
> 2013-01-02T02:24:58+01:00 DEBUG: [12810]  
> Horde_Core_ActiveSync_Driver::getServerChanges(INBOX, 1357089467,  
> 1357089898, 0, 1)
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Found 0 message changes in INBOX.
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing state for  
> collection: @Tasks@, synckey: {xxx-xxx-xxx-xxx}2
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Loading state for synckey  
> {xxx-xxx-xxx-xxx}2
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing message diff  
> engine for @Tasks@
> 2013-01-02T02:24:58+01:00 DEBUG: [12810]  
> Horde_Core_ActiveSync_Driver::getServerChanges(@Tasks@, 1357088640,  
> 1357089898, 0, 1)
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Found 0 message changes in @Tasks at .
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing state for  
> collection: @Contacts@, synckey: {xxx-xxx-xxx-xxx}4
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Loading state for synckey  
> {xxx-xxx-xxx-xxx}4
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing message diff  
> engine for @Contacts@
> 2013-01-02T02:24:58+01:00 DEBUG: [12810]  
> Horde_Core_ActiveSync_Driver::getServerChanges(@Contacts@,  
> 1357088655, 1357089898, 0, 1)
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Found 0 message changes in  
> @Contacts at .
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing state for  
> collection: @Calendar@, synckey: {xxx-xxx-xxx-xxx}2
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Loading state for synckey  
> {xxx-xxx-xxx-xxx}2
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Initializing message diff  
> engine for @Calendar@
> 2013-01-02T02:24:58+01:00 DEBUG: [12810]  
> Horde_Core_ActiveSync_Driver::getServerChanges(@Calendar@,  
> 1357088640, 1357089898, 0, 1)
> 2013-01-02T02:24:58+01:00 DEBUG: [12810] Found 0 message changes in  
> @Calendar at .


Yes, these are normal PING requests. It's how the device listens for  
changes. It will continue until the HEARTBEAT elapses or a change is  
detected then a new PING request is issued.
-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6062 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/horde/attachments/20130101/776a08b2/attachment-0001.bin>