Bug #56354 | MySQL Crash | ||
---|---|---|---|
Submitted: | 30 Aug 2010 0:39 | Modified: | 30 Aug 2010 13:15 |
Reporter: | allison vollmann | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 5.0 / 5.1 | OS: | Linux (Debian Lenny) |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysql innodb crash |
[30 Aug 2010 0:39]
allison vollmann
[30 Aug 2010 0:41]
allison vollmann
mysqld report
Attachment: mysql.log (text/x-log), 51.51 KiB.
[30 Aug 2010 4:22]
Valeriy Kravchuk
What exact version of MySQL server, 5.x.y, do you use? Had you tried to use forced recovery, as suggested in the log?
[30 Aug 2010 13:15]
allison vollmann
Version: mysqld Ver 5.1.47-1~bpo50+1 for debian-linux-gnu on x86_64 ((Debian)) with argument: mysqld --innodb-force-recovery=6 (max level) the problem has been fixed Thanks