Carol Tardif wrote:
[...]
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?
edit your cyrus.conf and change the following option
EVENTS {
# this is required
checkpoint cmd="ctl_cyrusdb -c" period=30
}
this is how
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 impor
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:
João Assad wrote:
Carol Tardif wrote:
Hello,
We are using Cyrus-2.2.10 in a Murder environnement with two
backend +200K mailboxes each. Since our upgrade from Red Hat 7.3
to RHEL 3.0 AS we get this error:
May 19 13:56:07 mupdate mupdate[26023]: DBERROR: skiplist recovery
/var/imap/mailboxes.db: 45
Carol Tardif wrote:
Hello,
We are using Cyrus-2.2.10 in a Murder environnement with two
backend +200K mailboxes each. Since our upgrade from Red Hat 7.3
to RHEL 3.0 AS we get this error:
May 19 13:56:07 mupdate mupdate[26023]: DBERROR: skiplist recovery
/var/imap/mailboxes.db: 45DF894 should be AD
