Facebook
Twitter
A
AndyD
Guest
My server crashed, so I got it rebooted, but when it came back up MySQL wasn't started. So I attempted to restart it, but it didn't start.
I checked my logs and attempted to run it again and got the following:
I've been trying to restart it a few times, and this time it said:
And I was 'tail'ing my syslog, which showed this:
What now?
I checked my logs and attempted to run it again and got the following:
Code:
Aug 7 15:46:08 serv02 mysqld_safe[5347]: started
Aug 7 15:46:16 serv02 mysqld[5350]: 060807 15:46:16 InnoDB: Database was not shut down normally!
Aug 7 15:46:16 serv02 mysqld[5350]: InnoDB: Starting crash recovery.
Aug 7 15:46:16 serv02 mysqld[5350]: InnoDB: Reading tablespace information from the .ibd files...
Aug 7 15:46:17 serv02 mysqld[5350]: InnoDB: Restoring possible half-written data pages from the doublewrite
Aug 7 15:46:17 serv02 mysqld[5350]: InnoDB: buffer...
Aug 7 15:46:27 serv02 kernel: VM: killing process mysqld
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: Error: tried to read 1048576 bytes at offset 0 2097152.
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: Was only able to read 544768.
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: Fatal error: cannot read from file. OS error number 17.
Aug 7 15:46:27 serv02 mysqld[5350]: 060807 15:46:27InnoDB: Assertion failure in thread 16384 in file os0file.c line 2133
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: We intentionally generate a memory trap.
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: Submit a detailed bug report to [url]http://bugs.mysql.com.[/url]
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: If you get repeated assertion failures or crashes, even
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: immediately after the mysqld startup, there may be
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: [url]http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html[/url]
Aug 7 15:46:27 serv02 mysqld[5350]: InnoDB: about forcing recovery.
Aug 7 15:46:27 serv02 mysqld[5350]: mysqld got signal 11;
Aug 7 15:46:27 serv02 mysqld[5350]: This could be because you hit a bug. It is also possible that this binary
Aug 7 15:46:27 serv02 mysqld[5350]: or one of the libraries it was linked against is corrupt, improperly built,
Aug 7 15:46:27 serv02 mysqld[5350]: or misconfigured. This error can also be caused by malfunctioning hardware.
Aug 7 15:46:27 serv02 mysqld[5350]: We will try our best to scrape up some info that will hopefully help diagnose
Aug 7 15:46:27 serv02 mysqld[5350]: the problem, but since we have already crashed, something is definitely wrong
Aug 7 15:46:27 serv02 mysqld[5350]: and this may fail.
Aug 7 15:46:27 serv02 mysqld[5350]:
Aug 7 15:46:27 serv02 mysqld[5350]: key_buffer_size=0
Aug 7 15:46:27 serv02 mysqld[5350]: read_buffer_size=2093056
Aug 7 15:46:27 serv02 mysqld[5350]: max_used_connections=0
Aug 7 15:46:27 serv02 mysqld[5350]: max_connections=100
Aug 7 15:46:27 serv02 mysqld[5350]: threads_connected=0
Aug 7 15:46:27 serv02 mysqld[5350]: It is possible that mysqld could use up to
Aug 7 15:46:27 serv02 mysqld[5350]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 409199 K
Aug 7 15:46:27 serv02 mysqld[5350]: bytes of memory
Aug 7 15:46:27 serv02 mysqld[5350]: Hope that's ok; if not, decrease some variables in the equation.
Aug 7 15:46:27 serv02 mysqld[5350]:
Aug 7 15:46:27 serv02 mysqld[5350]: thd=(nil)
Aug 7 15:46:27 serv02 mysqld[5350]: Attempting backtrace. You can use the following information to find out
Aug 7 15:46:27 serv02 mysqld[5350]: where mysqld died. If you see no messages after this, something went
Aug 7 15:46:27 serv02 mysqld[5350]: terribly wrong...
Aug 7 15:46:27 serv02 mysqld[5350]: Cannot determine thread, fp=0xbfffc208, backtrace may not be correct.
Aug 7 15:46:27 serv02 mysqld[5350]: Stack range sanity check OK, backtrace follows:
Aug 7 15:46:27 serv02 mysqld[5350]: 0x815460b
Aug 7 15:46:27 serv02 mysqld[5350]: 0x4005cd26
Aug 7 15:46:27 serv02 mysqld[5350]: 0x833849e
Aug 7 15:46:27 serv02 mysqld[5350]: 0x82f8af2
Aug 7 15:46:27 serv02 mysqld[5350]: 0x82af370
Aug 7 15:46:27 serv02 mysqld[5350]: 0x82e0081
Aug 7 15:46:27 serv02 mysqld[5350]: 0x82254c8
Aug 7 15:46:27 serv02 mysqld[5350]: 0x81d4852
Aug 7 15:46:27 serv02 mysqld[5350]: 0x81cbb15
Aug 7 15:46:27 serv02 mysqld[5350]: 0x8152fd5
Aug 7 15:46:27 serv02 mysqld[5350]: 0x81564e5
Aug 7 15:46:27 serv02 mysqld[5350]: 0x4020f3be
Aug 7 15:46:27 serv02 mysqld[5350]: 0x80ede51
Aug 7 15:46:27 serv02 mysqld[5350]: New value of fp=(nil) failed sanity check, terminating stack trace!
Aug 7 15:46:27 serv02 mysqld[5350]: Please read [url]http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html[/url] and follow instructions on how to resolve the stack trace. Resolved
Aug 7 15:46:27 serv02 mysqld[5350]: stack trace is much more helpful in diagnosing the problem, so please do
Aug 7 15:46:27 serv02 mysqld[5350]: resolve it
Aug 7 15:46:27 serv02 mysqld[5350]: The manual page at [url]http://www.mysql.com/doc/en/Crashing.html[/url] contains
Aug 7 15:46:27 serv02 mysqld[5350]: information that should help you find out what is causing the crash.
Aug 7 15:46:27 serv02 pop3d: Unable to connect to the mysql database
Aug 7 15:46:27 serv02 pop3d: Unable to connect to the mysql database
Aug 7 15:46:27 serv02 mysqld_safe[5363]: ended
Aug 7 15:46:34 serv02 /etc/init.d/mysql[5456]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Aug 7 15:46:34 serv02 /etc/init.d/mysql[5456]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Aug 7 15:46:34 serv02 /etc/init.d/mysql[5456]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
Aug 7 15:46:34 serv02 /etc/init.d/mysql[5456]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Aug 7 15:46:34 serv02 /etc/init.d/mysql[5456]:I've been trying to restart it a few times, and this time it said:
Code:
serv02:~# /etc/init.d/mysql restart
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld/etc/init.d/mysql: line 68: 9126 Segmentation fault $SELF start
serv02:~#And I was 'tail'ing my syslog, which showed this:
Code:
Aug 7 16:24:20 serv02 mysqld[8925]: /usr/sbin/mysqld: ready for connections.
Aug 7 16:24:20 serv02 mysqld[8925]: Version: '4.1.14-Debian_6-log' socket: '/v ar/run/mysqld/mysqld.sock' port: 3306 Source distribution
Aug 7 16:24:44 serv02 mysqld[8925]: 060807 16:24:44 [ERROR] /usr/sbin/mysqld: C an't open file: 'phpbb_sessions.MYI' (errno: 145)
Aug 7 16:24:44 serv02 mysqld[8925]: 060807 16:24:44 [ERROR] /usr/sbin/mysqld: C an't open file: 'phpbb_sessions.MYI' (errno: 145)
Aug 7 16:24:47 serv02 mysqld[8925]: 060807 16:24:47 [ERROR] /usr/sbin/mysqld: C an't open file: 'phpbb_sessions.MYI' (errno: 145)
Aug 7 16:24:49 serv02 mysqld[8925]: 060807 16:24:49 [ERROR] /usr/sbin/mysqld: C an't open file: 'phpbb_sessions.MYI' (errno: 145)
Aug 7 16:24:49 serv02 mysqld[8925]: 060807 16:24:49 [ERROR] /usr/sbin/mysqld: C an't open file: 'phpbb_sessions.MYI' (errno: 145)
Aug 7 16:25:42 serv02 kernel: VM: killing process mysqld
Aug 7 16:28:21 serv02 kernel: VM: killing process mysqladmin
Aug 7 16:28:25 serv02 kernel: VM: killing process mysqld
Aug 7 16:28:30 serv02 kernel: VM: killing process mysqladmin
Aug 7 16:28:38 serv02 kernel: VM: killing process mysqld
Aug 7 16:28:39 serv02 kernel: VM: killing process mysql
Aug 7 16:28:39 serv02 kernel: VM: killing process mysql
Aug 7 16:28:56 serv02 kernel: VM: killing process mysqladmin
Aug 7 16:28:56 serv02 kernel: VM: killing process mysql
Aug 7 16:28:56 serv02 kernel: VM: killing process mysql
Aug 7 16:28:56 serv02 kernel: Process mysql (pid: 9141, stackpage=da275000)
Aug 7 16:28:56 serv02 kernel: Process mysql (pid: 9126, stackpage=f4b8d000)What now?
