innodb crash after yum update

Last night I updated to the latest version of Percona 5.5 server.
I did a yum update then shutdown -r now (had to reboot for kernel updates)

MySQL was still running when I did this upgrade and wasn’t shutdown by the rpm scripts
because we have several instances running so they don’t use the default /etc/init.d/mysql init script.

Previous shutdown not from last night:

Normal shutdown happening:130201 23:11:39 [Note] /usr/sbin/mysqld: Normal shutdown130201 23:11:41 InnoDB: Starting shutdown…130201 23:11:46 InnoDB: Shutdown completed; log sequence number 665517551130201 23:11:46 [Note] /usr/sbin/mysqld: Shutdown complete130201 23:11:46 mysqld_safe mysqld from pid file /var/run/mysql/ endedStarting Back up:130201 23:11:47 mysqld_safe Starting mysqld daemon with databases from /data/mysql.spam

Last nights shutdown after yum update:

Not complete shutdown:130228 23:44:46 [Note] /usr/sbin/mysqld: Normal shutdown130228 23:44:46 [Note] Event Scheduler: Purging the queue. 0 eventsStarting back up:130228 23:47:15 mysqld_safe Starting mysqld daemon with databases from /data/mysql.spamInnoDB: The log sequence number in ibdata files does not matchInnoDB: the log sequence number in the ib_logfiles!130228 23:47:16 InnoDB: Database was not shut down normally!InnoDB: Starting crash recovery.InnoDB: Reading tablespace information from the .ibd files…InnoDB: Restoring possible half-written data pages from the doublewriteInnoDB: buffer…

So it looks like it started to shutdown but then didn’t complete properly?
Would installing new binaries before shutting down mysql cause this to happen?
The binaries should be in memory do I don’t see why it would.


Looks like it was not happened because of binaries update but when you shutdown with "shutdown -r ", it was shutdown at OS level that had not waited long enough to let normal shutdown completely. Probably MySQL had no chances to stop cleanly so it just got crash error and started recovery.