MySQL Bugs: #54354: MySQL Server Crash

Bug #54354	MySQL Server Crash
Submitted:	9 Jun 2010 5:42	Modified:	10 Jul 2010 20:49
Reporter:	Alice Wang	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.77-b13-log	OS:	Linux (Ubuntu)
Assigned to:		CPU Architecture:	Any
Tags:	MySQL self crash & recovery

Description:
Jun  3 00:27:48    mysqld[8884]: 100603  0:27:48 [Note] Starting crash recovery...
Jun  3 00:27:48    mysqld[8884]: 100603  0:27:48 [Note] Crash recovery finished.
Jun  3 00:27:48    mysqld[8884]: 100603  0:27:48 [Note] /usr/sbin/mysqld: ready for connections.

Jun  3 00:27:57    mysqld[8884]: 100603  0:27:57 [ERROR] /usr/sbin/mysqld: Table './mysql/proc' is marked as crashed and should be repaired
Jun  3 00:27:57    mysqld[8884]: 100603  0:27:57 [Warning] Checking table:   './mysql/proc'

How to repeat:
MySQL server crashed when it backup a particular database and the error massages indicate broken proc in that database.

Suggested fix:
Start to check all the tables and procedures, but there is no broken tables or procs. However, we run query to show all tables and got 2 warnings about the views' creator is no longer in the grants table. And I tried to open these views and also got error message from mysql.

To fix it
- drop these views 
- recreate with user who in grants table

Thank you for the report.

But version 5.0.77 is old and many bugs were fixed since. Please try version 5.0.91 and if problem still exists provide full error log, command line you use to call mysqldump and what mysqldump returns.

It is Innodb database and mysqldump command as the following
mysqldump --user --password --comments --opt --routines --triggers --no-data --flush-privileges ${DB} > ${DUMPFILE}

Please try 5.0.91 as Sveta asked before. Thanks in advance.

Upgrading MySQL 5.0.77 to MySQL 5.1 above or 5.1.47 (Current Release) directly will have more advantages? MySQL don't support 5.0 any more?

Thank you for the feedback.

This depends from your application if upgrading to version 5.1 has advantages of not. Please check list of new features and list of incompatibility changes, then decide if this is proper for you. Regarding to why I asked for upgrade to version 5.0.91 it is safe to upgrade to next minor release and is more clear if problem exists in this version or not. MySQL 5.0 is in extended support stage which means we will fix only security and some of crashing bugs and bugs which affect customers.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".