I also had this problem and fixed it. Unfortunately I did not record the exact fix although I do remember the cause. During the upgrade, the script attempts to convert the cyrus databases from (IIRC) Berkeley to Skiplist format. If it finds a corrupt db it fails and exits.
During start-up of cyrus and usually once a day (see cyrus.conf) the databases are checked with ctl_cyrusdb. Are there any log entries indicating corruption? See http://comments.gmane.org/gmane.mail.imap.cyrus/35023 for an example. The cure involves identifying the corrupt db, deleting it and allowing cyrus to re-create it on start up. tls_sessions.db is a favourite apparently. If it's deliver.db then you will have to re-mark messages as read. (I am assuming that mailboxes.db is OK although there are instructions out there for re-creating it). HTH On 07/04/14 09:44, Kristian Rink wrote: > Not so far. :( So far I just left the server running at its current > version and am scheduling a full re-install / move to new hardware with > copying post boxes on an IMAP level. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989609 Title: package cyrus-common-2.4 2.4.12-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-imapd-2.4/+bug/989609/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
