[Tickets #13825] Re: Remi PHP update to 5.5.21-1 results in constant resyncing
noreply at bugs.horde.org
noreply at bugs.horde.org
Fri Jan 23 15:02:22 UTC 2015
BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE
E-MAIL-ADRESSE WERDEN NICHT GELESEN.
Ticket-URL: https://bugs.horde.org/ticket/13825
------------------------------------------------------------------------------
Ticket | 13825
Aktualisiert Von | christian at hailer.eu
Zusammenfassung | Remi PHP update to 5.5.21-1 results in constant resyncing
Warteschlange | Synchronization
Version | FRAMEWORK_5_2
Typ | Bug
Status | Feedback
Priorität | 1. Low
Milestone |
Patch |
Zuständige |
------------------------------------------------------------------------------
christian at hailer.eu (2015-01-23 15:02) hat geschrieben:
>
>> Then I realized I updated PHP and that the php-imap package was among
>> the updates. I downgraded all PHP packages to the old version and
>> everything works like a charm now.
>
> Horde/IMP does not make use of the PHP bundled IMAP library. We use
> our own Horde_Imap_Client library. If this issue is, in fact, due to
> a PHP update, it is not from php-imap. Any other errors in the
> webserver error log, or the horde log?
>
>
Hello Michael,
no, there are no errors in any other logs, none in Apache, Dovecot,
normal Horde log...
>> The reason why I'm filing this bug is: I think Horde should handle
>> the above error message and tell the ActiveSync client to try again
>> later. I suspect that Horde reported back to the client that no
>> message at all is left in the folder it tried to sync when the error
>> occurs, and with the next ping it is able to connect again and
>> resyncs all the messages.
>
> Normally, when an error such as the one you describe occurs, we
> report the error condition back to the client (as we should). What
> the client chooses to do with that information is out of our
> control. I'd have to see more context in the sync log to see if we
> are sending the most appropriate error code back or not. Depending
> on when the error occurs, and what the actual error is, we might not
> have the chance to send an error code back. Again, would need to see
> more context to know for sure.
>
>
here is a part of the sync log:
2015-01-23T09:00:07+01:00 INFO: [29742] Initializing state for
collection: INBOX.! Astrid, synckey:
{54854e18-3c50-4b6c-9de1-2bfd51a9e6c4}455
2015-01-23T09:00:07+01:00 INFO: [29742] Loading state for synckey
{54854e18-3c50-4b6c-9de1-2bfd51a9e6c4}455
2015-01-23T09:00:07+01:00 INFO: [29742] Initializing message diff
engine for F0eb0762a (INBOX.! Astrid)
2015-01-23T09:00:07+01:00 INFO: [29742]
Horde_Core_ActiveSync_Driver::getSyncStamp(INBOX.! Astrid, 1421928788);
2015-01-23T09:00:07+01:00 INFO: [29742] Using SYNCSTAMP 1422000007 for
F0eb0762a.
2015-01-23T09:00:07+01:00 INFO: [29742]
Horde_Core_ActiveSync_Driver::getServerChanges(INBOX.! Astrid,
1421928788, 1422000007, 0, 1, 1, 100, )
2015-01-23T09:00:07+01:00 INFO: [29742] INBOX.! Astrid IMAP MODSEQ: 1431
2015-01-23T09:00:07+01:00 ERR: IMAP error reported by server.
2015-01-23T09:00:08+01:00 INFO: [29742] Found 0 message changes in F0eb0762a.
Some minutes later when the IMAP error is gone it's resyncing the folder:
2015-01-23T09:05:34+01:00 INFO: [29782] Initializing state for
collection: INBOX.! Astrid, synckey:
{54854e18-3c50-4b6c-9de1-2bfd51a9e6c4}455
2015-01-23T09:05:34+01:00 INFO: [29782] Loading state for synckey
{54854e18-3c50-4b6c-9de1-2bfd51a9e6c4}455
2015-01-23T09:05:34+01:00 INFO: [29782] Initializing message diff
engine for F0eb0762a (INBOX.! Astrid)
2015-01-23T09:05:34+01:00 INFO: [29782]
Horde_Core_ActiveSync_Driver::getSyncStamp(INBOX.! Astrid, 1421928788);
2015-01-23T09:05:34+01:00 INFO: [29782] Using SYNCSTAMP 1422000334 for
F0eb0762a.
2015-01-23T09:05:34+01:00 INFO: [29782]
Horde_Core_ActiveSync_Driver::getServerChanges(INBOX.! Astrid,
1421928788, 1422000334, 0, 0, 1, 100, )
2015-01-23T09:05:34+01:00 INFO: [29782] INBOX.! Astrid IMAP MODSEQ: 1431
2015-01-23T09:05:34+01:00 WARN: [29782] FOLDERSYNC required, collection gone.
2015-01-23T09:05:34+01:00 DEBUG: [29782] O <Folder>
2015-01-23T09:05:34+01:00 DEBUG: [29782] O <SyncKey>
2015-01-23T09:05:34+01:00 DEBUG: [29782] O
{54854e18-3c50-4b6c-9de1-2bfd51a9e6c4}455
2015-01-23T09:05:34+01:00 DEBUG: [29782] O </SyncKey>
2015-01-23T09:05:34+01:00 DEBUG: [29782] O <FolderId>
2015-01-23T09:05:34+01:00 DEBUG: [29782] O F0eb0762a
2015-01-23T09:05:34+01:00 DEBUG: [29782] O </FolderId>
2015-01-23T09:05:34+01:00 DEBUG: [29782] O <Status>
2015-01-23T09:05:34+01:00 DEBUG: [29782] O 12
2015-01-23T09:05:34+01:00 DEBUG: [29782] O </Status>
2015-01-23T09:05:34+01:00 DEBUG: [29782] O </Folder>
More information about the bugs
mailing list