After Cyrus upgrade 2.3.16 to 2.4.5: Sync_client bailing out

[Bron Gondwana]

That all looks fine.  Are you able to capture telemetry data?

Did you read the output of the reconstruct?  Did it say anything about
GUID errors at any point? That's the one thing that -G by itself can't
fix - you need to make a decision to keep or delete the message (because
GUID errors mean filesystem corruption - so you really need to know if
it's the cyrus.index or the underlying spool files that are corrupted
before making your choice!)

Anyway - the telemetry data on the replication user should pinpoint the
exact problem pretty quickly.

Regards,

Bron.

On Wed, Jan 26, 2011 at 01:43:43PM +0100, Martin Schweizer wrote:
> Sorry I forgot the relevant part of mailbox.db:
> 
> user.mdemonaco  0 default mdemonaco     lrswipkxtecda
> user.mdemonaco.Drafts   0 default mdemonaco     lrswipkxtecda
> user.mdemonaco.Sent     0 default mdemonaco     lrswipkxtecda
> user.mdemonaco.Trash    0 default mdemonaco     lrswipkxtecda
> 
> 
> 2011/1/26 Patrick Boutilier <boutilpj at ednet.ns.ca>:
> > On 01/26/2011 06:12 AM, Patrick Boutilier wrote:
> >> On 01/26/2011 04:34 AM, Martin Schweizer wrote:
> >>> Hello
> >>>
> >>> I upgraded both server (master and client). After restart the sync I
> >>> get a lot of messages like them (on different mailboxes):
> >>>
> >>> (sync_client)
> >>> Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: MAILBOX received NO
> >>> response: System I/O error
> >>> Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: do_folders(): update
> >>> failed: user.mdemonaco.Sent 'The remote Server(s) denied the
> >>> operation'
> >>> Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: IOERROR: The remote
> >>> Server(s) denied the operation
> >>> Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: Error in do_sync():
> >>> bailing out! The remote Server(s) denied the operation
> >>> Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: Processing sync log
> >>> file /usr/imap/var/imap/sync/log-56473 failed: The remote Server(s)
> >>> denied the operation
> >>> Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: Reprocessing sync log
> >>> file /usr/imap/var/imap/sync/log-56473
> >>>
> >>> (sync_server)
> >>> Jan 26 09:15:14 acsvfbsd04 syncserver[14859]: IOERROR: failed to parse
> >>> /usr/imap/var/spool/imap/sync./14859/33c1d7401877b45e7071d86922b79a6361afd25e
> >>> Jan 26 09:15:14 acsvfbsd04 syncserver[14859]: Failed to append file
> >>> user.mdemonaco.Sent 2
> >>
> >>
> >> Does the mailbox 'user.mdemonaco.Sent 2' exist on the sync_server ? I
> >> have seen the same thing in 2.3.16 .
> >
> > I meant exist in the filesystem. When I see that error in 2.3.16 the
> > mailbox exists in mailboxes.db but not on the filesystem.
> >
> >
> >
> >>
> >>
> >>
> >>
> >>>
> >>> Of course I did a recontruct -r -G on all mailboxes (as user cyrus). I
> >>> did it on the sync_client and on the sync_server. Sometimes the
> >>> messages comes again, sometimes the same mailbox get the same error
> >>> messages etc. So I have no idea what I have to do now. The sync with
> >>> the previous version (2.3.16) runs without any problems.
> >>>
> >>> Any hints are welcome.
> >>>
> >>> Regards,
> >>
> >> ----
> >> Cyrus Home Page: http://www.cyrusimap.org/
> >> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> >
> > ----
> > Cyrus Home Page: http://www.cyrusimap.org/
> > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> >
> 
> 
> 
> -- 
> Martin Schweizer
> schweizer.martin at gmail.com
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/