2.5.7 -> 2.5.7 initial replication fails - failed to parse?

Karl Pielorz kpielorz_lst at tdx.co.uk
Thu Apr 21 05:28:44 EDT 2016

--On 20 April 2016 13:15 -0400 Giles Malet <gdmalet at uwaterloo.ca> wrote:

> I can't answer your other questions, but deleting those directories is
> fine. The only one(s) possible in use are those whose name matches the
> PID of a running sync_server process. Perhaps best then to shut cyrus
> down on the replica, delete everything as above, then restart. And maybe
> run a reconstruct or two, on server and replica.

Removed the sync directories, it still failed. Looked carefully at the 
mailbox folder  on the master it was failing on:

% /usr/local/cyrus/bin/reconstruct -R user.authspam.CantProcess
user.mailbox.CantProcess uid 27 guid mismatch
user.mailbox.CantProcess uid 27 marking for uid upgrade
user.mailbox.CantProcess uid 28 guid mismatch
user.mailbox.CantProcess uid 28 marking for uid upgrade
user.mailbox.CantProcess uid 27 rediscovered - appending
user.mailbox.CantProcess uid 28 rediscovered - appending

Now the sync seems to be continuing.

Presumably there's no harm with running 'reconstruct -R' on "everything"? 
Though I do have a vague recollection of running that before after the data 
was snapshot'd from our current 2.4 server...


More information about the Cyrus-devel mailing list