Overnight, a script running from cron one of our servers (Ubuntu 12.04.2 LTS) applied updates to MySQL. Rather than taking a few minutes to do this, it appears to have taken over an hour and a half, and the databases were still offline at the point one of my colleagues rebooted the server.
What concerns me a little is that it appears to have been trying to apply a an older MySQL update for Ubuntu 12.04.2 and a newer update for Ubuntu 12.04.1 at the same time - is this normal, or do we have a problem with configuration on the server?
Excerpt from dpkg.log
2013-07-26 07:04:08 startup archives unpack 2013-07-26 07:48:00 upgrade mysql-server-5.5 5.5.31-0ubuntu0.12.04.2 5.5.32-0ubuntu0.12.04.1 2013-07-26 07:48:00 status half-configured mysql-server-5.5 5.5.31-0ubuntu0.12.04.2 2013-07-26 07:51:09 status unpacked mysql-server-5.5 5.5.31-0ubuntu0.12.04.2 .... <snip> .... 2013-07-26 07:54:06 status half-installed mysql-server-5.5 5.5.31-0ubuntu0.12.04.2 2013-07-26 07:54:12 status unpacked mysql-server-5.5 5.5.32-0ubuntu0.12.04.1 2013-07-26 07:54:12 status unpacked mysql-server-5.5 5.5.32-0ubuntu0.12.04.1 .... <snip> .... 2013-07-26 08:10:55 status half-configured mysql-server-5.5 5.5.32-0ubuntu0.12.04.1 2013-07-26 08:29:14 status installed mysql-server-5.5 5.5.32-0ubuntu0.12.04.1