Upgrading from 2.2.2-Beta to 2.2.8
p.boven at chello.nl
Sat Sep 4 01:56:38 EDT 2004
I've got a 2.2.2-beta-installation that has started to give us some
headaches: every few days, it will first get 'slow' (according to
complaints from the customer) and then it will stop listening to the
LMTP socket and IMAP port, and things just hang. I'm also finding
coredumps from mailbox_expunge in several mailboxes.
We've decided our best course of action would be to upgrade the customer
to 2.2.8 which we have running elsewhere already. I've done a first
test-migration, setting up a 2.2.2-beta system and then removing the
Cyrus Imap binaries and installing the 2.2.8-package on it. Seemed to
work just great.
Which brings me to my main question: Are there any things I need to
worry about when doing such an upgrade? Do I need to take care of
possible mailbox-corruption first, and if so, how? Any chance that some
DBs have changed type between 2.2.2-Beta and 2.2.8?
Regards, Paul Boven.
 stacktrace from those cores (they're all the same)
00020d08 cmd_expunge (11a088, 0, ffc00, 8e76ea04, 0, 1) + 40
0001ab90 cmdloop (0, 1124c8, 0, 0, 0, 100400) + bc0
00019dc0 service_main (0, 10f998, ffbffd9c, 1, ffbff918, 1) + 2f8
000189bc main (1, ffbffd94, 3c, fa, 10f000, 0) + 4c8
000180c0 _start (0, 0, 0, 0, 0, 0) + 5c
Systems in question are all Solaris 9.
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
More information about the Info-cyrus