[arch-general] mysql won't start after upgrade
I just upgraded MySQL on my Arch box to the latest version (5.1.33-1), and all of a sudden, MySQL won't start. I get the following in my mysql.err file (in /var/lib/mysql): 090412 07:53:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist 090412 7:53:21 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 16777216 bytes! 090412 7:53:21 [ERROR] Plugin 'InnoDB' init function returned error. 090412 7:53:21 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 090412 7:53:21 [ERROR] /usr/sbin/mysqld: unknown variable 'innodb_log_arch_dir=/var/lib/mysql' 090412 7:53:21 [ERROR] Aborting 090412 7:53:21 [Warning] Forcing shutdown of 2 plugins 090412 7:53:21 [Note] /usr/sbin/mysqld: Shutdown complete 090412 07:53:21 mysqld_safe mysqld from pid file /var/lib/mysql/humidor.pid ended I run mysql_upgrade, as instructed, but it also doesn't work. It expects a working daemon of MySQL, which as the above log output attests, isn't available. Can someone help?! Until this upgrade, MySQL has run flawlessly for years. Thanks, Scott
Em Domingo 12 Abril 2009, às 12:36:05, Scott Weisman escreveu:
I just upgraded MySQL on my Arch box to the latest version (5.1.33-1), and all of a sudden, MySQL won't start.
I get the following in my mysql.err file (in /var/lib/mysql):
090412 07:53:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist 090412 7:53:21 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 16777216 bytes! 090412 7:53:21 [ERROR] Plugin 'InnoDB' init function returned error. 090412 7:53:21 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 090412 7:53:21 [ERROR] /usr/sbin/mysqld: unknown variable 'innodb_log_arch_dir=/var/lib/mysql' 090412 7:53:21 [ERROR] Aborting 090412 7:53:21 [Warning] Forcing shutdown of 2 plugins 090412 7:53:21 [Note] /usr/sbin/mysqld: Shutdown complete 090412 07:53:21 mysqld_safe mysqld from pid file /var/lib/mysql/humidor.pid ended
I run mysql_upgrade, as instructed, but it also doesn't work. It expects a working daemon of MySQL, which as the above log output attests, isn't available.
Can someone help?! Until this upgrade, MySQL has run flawlessly for years.
Thanks,
Scott
Hi Scott, Delete this file: /var/lib/mysql/ib_logfile0 If this not work, try read the following threads: http://forums.mysql.com/read.php?22,144428,241055#msg-241055 http://venublog.com/2008/04/23/simple-way-to-crash-innodb-plugin-10/ http://bugs.mysql.com/bug.php?id=20851
On Sun, 2009-04-12 at 13:00 -0300, Douglas Soares de Andrade wrote:
Hi Scott,
Delete this file:
/var/lib/mysql/ib_logfile0
If this not work, try read the following threads:
http://forums.mysql.com/read.php?22,144428,241055#msg-241055 http://venublog.com/2008/04/23/simple-way-to-crash-innodb-plugin-10/ http://bugs.mysql.com/bug.php?id=20851
I don't think deleting the innodb transaction log is a good thing to do. If something is in that log which hasn't been committed to the innodb pool file, those transactions are lost.
participants (3)
-
Douglas Soares de Andrade
-
Jan de Groot
-
Scott Weisman