Problems with mupdate server.

Carol Tardif carol.tardif at
Fri May 20 13:48:42 EDT 2005

João Assad wrote:
> Carol Tardif wrote:
>> [...]
>> One thing I would like to know is instead of synchronising everything 
>> can I:
>>     1- delete mailboxe.db on mupdate.
>>     2- do "ctl_mboxlist -d -f /var/imap/mailboxes.db > 
>> mailbox_backend1.txt"
>>           on both backends
>>     3- Then on the mupdate import mailbox via:
>>       ctl_mboxlist -u -f /var/imap/mailboxes.db < mailbox_backend1.txt
>>       ctl_mboxlist -u -f /var/imap/mailboxes.db < mailbox_backend2.txt
>> Is this gonna work? Or I am forced to have a big downtime waiting for 
>> "ctl_mboxlist -m"
>> on both backends.
> Unfortunately it wont work and according to the devs, it should never 
> work that way, because this way you could potentially create 
> inconsistencies on the master server.
> Fortunately there is a patch that add this capacity to ctl_mboxlist, you 
> can find it here:
> But as I mentioned above, you can easily end up with an inconsistent 
> mailbox list on your master server.

Thanks for the explanation.

So now that I know that my mailboxes.db can get corrupted what can I do to
get away from long downtimes?

Can I have a backup mupdate server?

Can I backup my mupdate mailboxes.db so that when corruption occured, I stop cyrus
on mupdate then copy the backup mailboxes.db file then start again cyrus?
If I can do that at least this can give me time to find out how corruption happenned.

Is there any doc to help me understand how mailbox info is keep updated between
frontend, mupdate and backend.

This is the fisrt time that corruption happenned since we move from berkeley to
skiplist db. So I'm wondering what happened.


Carol Tardif
Cyrus Home Page:
Cyrus Wiki/FAQ:
List Archives/Info:

More information about the Info-cyrus mailing list