Re: Weird sync problems in 2.4.0
Hi Bron, the permissions are correct. If I run reconstruct -G I get a uid xxx guid mismatch message for a certain mail each time (although this message is not in the mailbox sync_client is choking on). Shouldn't reconstruct -G take care of this ? Regards Stephan Am Wednesday 13 October 2010 23:13:20 schrieben Sie: On Wed, Oct 13, 2010 at 09:13:24PM +0200, steff...@gmx.de wrote: Yes, I ran reconstruct -G a couple of times. Can you check the permissions on ths spool directories and the sync. directory? That's the next thing I can think of... Bron ( they all have to be writable by the Cyrus user ) Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Weird sync problems in 2.4.0
On Fri, Oct 15, 2010 at 08:40:40PM +0200, steff...@gmx.de wrote: Hi Bron, the permissions are correct. If I run reconstruct -G I get a uid xxx guid mismatch message for a certain mail each time (although this message is not in the mailbox sync_client is choking on). Shouldn't reconstruct -G take care of this ? Now that would have been nice to know about earlier. Error messages matter. That is actually the message that sync_client is choking on - though sync_client could probably be nicer about the error. Actually, you're right - with the correct flags reconstruct -G should be taking care of it, and not implementing those flags is my fault. I'll have to add another flag for this, because it's messy to fix. Basically it means you've had file corruption - and you need to decide if you want to create a brand new message with the corrupted content, or try to restore the old file from backup. At least that's how we've been treating it at FastMail. For now - just go and look at the message on your spool - the corruption will probably be pretty obvious! Then unlink the offending message and re-run reconstruct. It should fix your replication. For later - I'm adding extra flags to reconstruct that will be useful in this situation. They'll be in the next release. Regards, Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Weird sync problems in 2.4.0
Hello everybody, I have a problem regarding the synchronisation in 2.4.0. I installed 2.4.0 on two test servers where 2.3.16 was installed. The imapd on the replica hasn't been running for a while. After the two where online I tried to replicate from the master to the replica and ran into some problems. If I try to sync the mailbox user.tester to the replica using sync_client -v -m user.tester I get MAILBOXES user.tester Error from do_mailboxes(): bailing out! On the replica I can see the following error in syslog: IOERROR: failed to parse /path/to/sync./18755/991ebe63638ae2e25b9f081aa5b3d78f9380309b Failed to append file user.tester 29 I ran reconstruct on the mailbox for a dozen times using -G -r and -f but that didn't help. Browsing a bit through the source code (I am not a programmer) I found the message probably gets generated in message_parse in imap/message.c. I inserted a syslog message telling me which file it was trying to open and a sleep, recompiled and installed and tried to find the file the next time- it wasn't there, the directory where it should have been was empty. Using strace I can see that the sync_client is sending (amongst other stuff) APPLY MESSAGE whith a message and shortly after that a APPLY MAILBOX in which a GUID appears which is identical to the name of the file which is missing on the replica. How do I resolve that and is there a document describing the sync protocol in detail ? -- GMX DSL Doppel-Flat ab 19,99 euro;/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Weird sync problems in 2.4.0
Are you reconstructing with -G? My best guess is the original file is corrupt, but without -G it won't notice! steff...@gmx.de wrote: Hello everybody, I have a problem regarding the synchronisation in 2.4.0. I installed 2.4.0 on two test servers where 2.3.16 was installed. The imapd on the replica hasn't been running for a while. After the two where online I tried to replicate from the master to the replica and ran into some problems. If I try to sync the mailbox user.tester to the replica using sync_client -v -m user.tester I get MAILBOXES user.tester Error from do_mailboxes(): bailing out! On the replica I can see the following error in syslog: IOERROR: failed to parse /path/to/sync./18755/991ebe63638ae2e25b9f081aa5b3d78f9380309b Failed to append file user.tester 29 I ran reconstruct on the mailbox for a dozen times using -G -r and -f but that didn't help. Browsing a bit through the source code (I am not a programmer) I found the message probably gets generated in message_parse in imap/message.c. I inserted a syslog message telling me which file it was trying to open and a sleep, recompiled and installed and tried to find the file the next time- it wasn't there, the directory where it should have been was empty. Using strace I can see that the sync_client is sending (amongst other stuff) APPLY MESSAGE whith a message and shortly after that a APPLY MAILBOX in which a GUID appears which is identical to the name of the file which is missing on the replica. How do I resolve that and is there a document describing the sync protocol in detail ? -- GMX DSL Doppel-Flat ab 19,99 euro;/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
