[Tickets #11754] Re: ActiveSync won't push new emails to mobile device
bugs at horde.org
bugs at horde.org
Sun Dec 2 21:52:15 UTC 2012
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/11754
------------------------------------------------------------------------------
Ticket | 11754
Updated By | Michael Rubinsky <mrubinsk at horde.org>
Summary | ActiveSync won't push new emails to mobile device
Queue | Synchronization
Version | Git master
Type | Bug
State | Unconfirmed
Priority | 2. Medium
Milestone |
Patch |
-Owners |
+Owners | Michael Rubinsky
------------------------------------------------------------------------------
Michael Rubinsky <mrubinsk at horde.org> (2012-12-02 21:52) wrote:
> Something that caught my eye in that log file - I have various
> "ERR:" entries, usually a pointer to trouble:
>
> 2012-11-25T14:22:39+00:00 ERR: Unmatched content:
> 2012-11-25T14:22:39+00:00 ERR: Array
Normal, and harmless.
> 2012-11-25T14:22:44+00:00 ERR: Changes detected in sync_cache during
> wait interval, exiting without updating cache.
This means that more than one process is syncing the same collection
at the same time. So the current process dies, letting the first
process complete. This can sometimes occur when you explicitly trigger
a sync on the device while it is already PINGing.
> 2012-11-25T14:43:26+00:00 ERR: Incrementing counter, we saw this
> synckey before.
This means that, for whatever reason, the device did not receive
and/or understand the response to it's last request, so it is
repeating the request. We count the number of times this happens to
prevent infinite sync loops.
> 2012-11-25T14:53:39+00:00 ERR: [5199] State gone, PING terminating
> and forcing a SYNC:
This means that the current syncState has been removed, as would
happen when you remove the device from Horde (or manually from the DB).
> 2012-11-25T15:08:28+00:00 ERR: [5323] PING terminating: Empty
> synckey for INBOX
This is similar error to the above error that occurs when the state is
removed during a running PING.
> Most of these appear several times, but not necessarily in a
> specific pattern.
Without more information, it's impossible to tell what is wrong. The
error messages above can all be attributed to normal/expected behavior.
More information about the bugs
mailing list