Hello,
Il have started the upgrade of my murder infrastructure and I face
several problems.
Context :
- 30 backends in self made cyrus 3.2.6 (Debian packages with
last patches).
- Several frontend in cyrus 3.2
- one mupdate in 3.2
Cyrus Imapd docs : « Generally accepted wisdom when upgrading a Murder
configuration is to upgrade all your back end servers first. This can
be done one at a time. Upgrade your mupdate master and front ends
last. »
and
« If you're familiar with replication, and your current installation
is 2.4 or newer, you can set up your existing installation to
replicate data to a new 3.8 installation and failover to the new
installation when you're ready. »
All backends are replicated to 3.8.1-1~bpo12 fome debian's backport to
Bookworm.
3 replicated backends in 3.8 version are now in production.
First problem. There will be two other mails.
1) All three 3.8 backends can't finish their 'ctl_mboxlist -m' :
mupdate said: DELETED.user.some.path.INBOX.Trash.2013-2017.66029CA6
backend-2-01!default A lrswipkxtecda
mailboxes.db said: DELETED.some.path.INBOX.Trash.2013.66029C93
backend-2-01!default A lrswipkxtecda
mupdate says: DELETED.user.some.path.INBOX.Trash.2013.66029C93
backend-2-01!default A lrswipkxtecda
fatal error: mupdate said not us before it said us
In mailboxes.db, Trash.2013-2017.66029CA6 uniqueid is 3c2e1144560afef7
Trash.2013.66029C93 uniqueid is 257f3428511b9c16.
DELETED.user.*.2013.66029C93 and DELETED.user.*.2013-2017.66029CA6 are
in mupdate mailboxes db.
Debian package
ctl_mboxlist -ma works fine and the backend can start.
But following 'ctl_mboxlist -m' still give the same error.
All three upgraded backends give similar errors.
One test server, with only one user mailbox and one shared mailbox
doesn't have the problem (3.2.6 mupdate vs 3.8.1-1~bpo12 backend).
These backends are now in production, and work fine, I can't go back
and retry.
Is this a known problem with a known solution ? If not (as I guess), how
can I help you help me with those backends ?
What should I do in order to successfully upgrade the others backends ?
Maybe going to 3.6 before 3.8 ? Maybe my 3.2's or my 3.8's are missing
some patch ?
Latest test : on test backend, using 3.8.3 version (sid's version
backported), one test mupdate using 3.2.12 (self made Debian package
based on Debian's las 3.2.6).
Backend can't start :
root@cyrus-backend-dev-02:~# cyrus ctl_mboxlist -C /tmp/imapd.conf -m
couldn't do LIST command on mupdate server
root@cyrus-backend-dev-02:~# cyrus ctl_mboxlist -C /tmp/imapd.conf -ma
couldn't do LIST command on mupdate server
Sincerly,
Jean Charles Delépine
--
Service systèmes et réseaux - DISI
Université de Picardie Jules Verne
5, rue du moulin neuf - 80000 Amiens
------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/Tfa45b4c4b5affc7d-M6bb66d25bec6f76fba35815e
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
