Has anybody else had problems with upgrading MySQL today?

The upgrade was to install the following packages: libmysqlclient16 mysql-client mysql-client-5.1 mysql-common mysql-server mysql-server-5.1 mysql-server-core-5.1

After installing the new server package, it attempted to stop and restart MySQL. Failed three times before it gave up and left me without a running database server.

I'm having a complete fail with fixing this. I'm running web sites and email off this server and I've just lost the whole kit and kaboodle - I'm not sure if there is a way to simply rollback with apt, so I tried to replace the non-working 5.1 packages with the 5.0 packages, which appears to be installing a whole new database right now because it's asking me to set a root password...

Oy.

This is in my daemon.log:

Feb 11 14:08:43 localhost /etc/init.d/mysql[29357]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Feb 11 14:08:43 localhost /etc/init.d/mysql[29357]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Feb 11 14:08:43 localhost /etc/init.d/mysql[29357]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Feb 11 14:08:43 localhost /etc/init.d/mysql[29357]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

Any help trying to figure this out would be greatly appreciated - all my other servers are running fine, but are useless without this one.

Somebody over on the Ubuntu forums found a fix for this, yay!

If you're on Ubuntu and you upgrade today only to find your MySQL server won't start, you need to edit your my.cnf and comment out the following two lines:

# log-bin=mysql-bin
# binlog_format=mixed

After completing that, running `apt-get -f install` should complete the package upgrade and restart your mysql server.