package: mysql-server-5.0 version: 5.0.18-7 severity: important
Since I upgraded to 5.0 from 4.1 mysqld has crashed regularly once an hour as a result of the same query:
Feb 11 21:41:40 lorien mysqld[18859]: thd->query at 0x8b461d0 = SELECT flag FROM bayes_seen
Feb 11 21:41:40 lorien mysqld[18859]: WHERE id = '2'Feb 11 21:41:40 lorien mysqld[18859]: AND msgid = '[EMAIL PROTECTED]'
In an effort to discover where the problem was I tried slightly different queries for the same information. The query should have returned no results, instead it seems to crash the server every single time. I don't know if this is related to #341705.
mysql> SELECT flag FROM bayes_seen WHERE msgid='[EMAIL PROTECTED]';
Empty set (0.43 sec) mysql> SELECT flag FROM bayes_seen WHERE id='2' LIMIT 10; +------+ | flag | +------+ | h | | h | | h | | h | | h | | h | | h | | h | | h | | h | +------+ 10 rows in set (0.04 sec) mysql> SELECT flag FROM bayes_seen WHERE id='2' AND flag='h' LIMIT 10; +------+ | flag | +------+ | h | | h | | h | | h | | h | | h | | h | | h | | h | | h | +------+ 10 rows in set (0.01 sec)mysql> SELECT flag FROM bayes_seen WHERE msgid='[EMAIL PROTECTED]' AND id='2';
ERROR 2013 (HY000): Lost connection to MySQL server during query ^ Crashes.mysql> SELECT flag FROM bayes_seen WHERE msgid='e41265bc4f1%' AND id='2';
ERROR 2013 (HY000): Lost connection to MySQL server during query ^ CrashesThe only applications using mysqld are spamassassin. I'm not sure what to do next to diagnose the problem..
Log messages:Feb 11 21:41:40 lorien mysqld[18859]: 060211 21:41:40InnoDB: Assertion failure in thread 2965867440 in file row0mysql.c line 341 Feb 11 21:41:40 lorien mysqld[18859]: InnoDB: Failing assertion: mbminlen == 1 Feb 11 21:41:40 lorien mysqld[18859]: InnoDB: We intentionally generate a memory trap. Feb 11 21:41:40 lorien mysqld[18859]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Feb 11 21:41:40 lorien mysqld[18859]: InnoDB: If you get repeated assertion failures or crashes, even Feb 11 21:41:40 lorien mysqld[18859]: InnoDB: immediately after the mysqld startup, there may be Feb 11 21:41:40 lorien mysqld[18859]: InnoDB: corruption in the InnoDB tablespace. Please refer to Feb 11 21:41:40 lorien mysqld[18859]: InnoDB: http://dev.mysql.com/ doc/mysql/en/Forcing_recovery.html
Feb 11 21:41:40 lorien mysqld[18859]: InnoDB: about forcing recovery. Feb 11 21:41:40 lorien mysqld[18859]: mysqld got signal 11;Feb 11 21:41:40 lorien mysqld[18859]: This could be because you hit a bug. It is also possible that this binary Feb 11 21:41:40 lorien mysqld[18859]: or one of the libraries it was linked against is corrupt, improperly built, Feb 11 21:41:40 lorien mysqld[18859]: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 11 21:41:40 lorien mysqld[18859]: We will try our best to scrape up some info that will hopefully help diagnose Feb 11 21:41:40 lorien mysqld[18859]: the problem, but since we have already crashed, something is definitely wrong
Feb 11 21:41:40 lorien mysqld[18859]: and this may fail. Feb 11 21:41:40 lorien mysqld[18859]: Feb 11 21:41:40 lorien mysqld[18859]: key_buffer_size=16777216 Feb 11 21:41:40 lorien mysqld[18859]: read_buffer_size=131072 Feb 11 21:41:40 lorien mysqld[18859]: max_used_connections=3 Feb 11 21:41:40 lorien mysqld[18859]: max_connections=100 Feb 11 21:41:40 lorien mysqld[18859]: threads_connected=2Feb 11 21:41:40 lorien mysqld[18859]: It is possible that mysqld could use up to Feb 11 21:41:40 lorien mysqld[18859]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
Feb 11 21:41:40 lorien mysqld[18859]: bytes of memoryFeb 11 21:41:40 lorien mysqld[18859]: Hope that's ok; if not, decrease some variables in the equation.
Feb 11 21:41:40 lorien mysqld[18859]: Feb 11 21:41:40 lorien mysqld[18859]: thd=0x8b27080Feb 11 21:41:40 lorien mysqld[18859]: Attempting backtrace. You can use the following information to find out Feb 11 21:41:40 lorien mysqld[18859]: where mysqld died. If you see no messages after this, something went
Feb 11 21:41:40 lorien mysqld[18859]: terribly wrong...Feb 11 21:41:40 lorien mysqld[18859]: Cannot determine thread, fp=0xb0c76aec, backtrace may not be correct. Feb 11 21:41:40 lorien mysqld[18859]: Stack range sanity check OK, backtrace follows:
Feb 11 21:41:40 lorien mysqld[18859]: 0x818f41c Feb 11 21:41:40 lorien mysqld[18859]: 0xffffe420 Feb 11 21:41:40 lorien mysqld[18859]: (nil) Feb 11 21:41:40 lorien mysqld[18859]: 0x8243f09 Feb 11 21:41:40 lorien mysqld[18859]: 0x81d90b5 Feb 11 21:41:40 lorien mysqld[18859]: 0x81d92ed Feb 11 21:41:40 lorien mysqld[18859]: 0x81e5424 Feb 11 21:41:40 lorien mysqld[18859]: 0x81e5eea Feb 11 21:41:40 lorien mysqld[18859]: 0x81ec708 Feb 11 21:41:40 lorien mysqld[18859]: 0x81ed010 Feb 11 21:41:40 lorien mysqld[18859]: 0x81a31a9 Feb 11 21:41:40 lorien mysqld[18859]: 0x81a899c Feb 11 21:41:40 lorien mysqld[18859]: 0x81a8fa6 Feb 11 21:41:40 lorien mysqld[18859]: 0x81aa128 Feb 11 21:41:40 lorien mysqld[18859]: 0x81aaa74 Feb 11 21:41:40 lorien mysqld[18859]: 0xb7fadcfd Feb 11 21:41:40 lorien mysqld[18859]: 0xb7def13eFeb 11 21:41:40 lorien mysqld[18859]: New value of fp=(nil) failed sanity check, terminating stack trace! Feb 11 21:41:40 lorien mysqld[18859]: Please read http:// dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved Feb 11 21:41:40 lorien mysqld[18859]: stack trace is much more helpful in diagnosing the problem, so please do
Feb 11 21:41:40 lorien mysqld[18859]: resolve it Feb 11 21:41:40 lorien mysqld[18859]: Trying to get some variables.Feb 11 21:41:40 lorien mysqld[18859]: Some pointers may be invalid and cause the dump to abort... Feb 11 21:41:40 lorien mysqld[18859]: thd->query at 0x8b461d0 = SELECT flag FROM bayes_seen
Feb 11 21:41:40 lorien mysqld[18859]: WHERE id = '2'Feb 11 21:41:40 lorien mysqld[18859]: AND msgid = '[EMAIL PROTECTED]'
Feb 11 21:41:40 lorien mysqld[18859]: thd->thread_id=5Feb 11 21:41:40 lorien mysqld[18859]: The manual page at http:// www.mysql.com/doc/en/Crashing.html contains Feb 11 21:41:40 lorien mysqld[18859]: information that should help you find out what is causing the crash. Feb 11 21:41:40 lorien mysqld_safe[22606]: Number of processes running now: 0
Feb 11 21:41:40 lorien mysqld_safe[22608]: restartedFeb 11 21:41:40 lorien mysqld[22611]: 060211 21:41:40 InnoDB: Database was not shut down normally!
Feb 11 21:41:40 lorien mysqld[22611]: InnoDB: Starting crash recovery.Feb 11 21:41:40 lorien mysqld[22611]: InnoDB: Reading tablespace information from the .ibd files... Feb 11 21:41:40 lorien mysqld[22611]: InnoDB: Restoring possible half- written data pages from the doublewrite
Feb 11 21:41:40 lorien mysqld[22611]: InnoDB: buffer...Feb 11 21:41:41 lorien mysqld[22611]: 060211 21:41:41 InnoDB: Starting log scan based on checkpoint at Feb 11 21:41:41 lorien mysqld[22611]: InnoDB: log sequence number 0 2010073658. Feb 11 21:41:41 lorien mysqld[22611]: InnoDB: Doing recovery: scanned up to log sequence number 0 2010076512 Feb 11 21:41:41 lorien mysqld[22611]: 060211 21:41:41 InnoDB: Starting an apply batch of log records to the database... Feb 11 21:41:41 lorien mysqld[22611]: InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
Feb 11 21:41:41 lorien mysqld[22611]: InnoDB: Apply batch completedFeb 11 21:41:41 lorien mysqld[22611]: InnoDB: Last MySQL binlog file position 0 98, file name /var/log/mysql/mysql-bin.000898 Feb 11 21:41:41 lorien mysqld[22611]: 060211 21:41:41 InnoDB: Started; log sequence number 0 2010076512 Feb 11 21:41:41 lorien mysqld[22611]: 060211 21:41:41 [Note] Recovering after a crash using /var/log/mysql/mysql-bin Feb 11 21:41:41 lorien mysqld[22611]: 060211 21:41:41 [Note] Starting crash recovery... Feb 11 21:41:41 lorien mysqld[22611]: 060211 21:41:41 [Note] Crash recovery finished. Feb 11 21:41:41 lorien mysqld[22611]: 060211 21:41:41 [Note] /usr/ sbin/mysqld: ready for connections. Feb 11 21:41:41 lorien mysqld[22611]: Version: '5.0.18-Debian_7-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian Etch distribution Feb 11 22:15:40 lorien mysqld[22611]: 060211 22:15:40InnoDB: Assertion failure in thread 2965736368 in file row0mysql.c line 341 Feb 11 22:15:40 lorien mysqld[22611]: InnoDB: Failing assertion: mbminlen == 1 Feb 11 22:15:40 lorien mysqld[22611]: InnoDB: We intentionally generate a memory trap. Feb 11 22:15:40 lorien mysqld[22611]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Feb 11 22:15:40 lorien mysqld[22611]: InnoDB: If you get repeated assertion failures or crashes, even Feb 11 22:15:40 lorien mysqld[22611]: InnoDB: immediately after the mysqld startup, there may be Feb 11 22:15:40 lorien mysqld[22611]: InnoDB: corruption in the InnoDB tablespace. Please refer to Feb 11 22:15:40 lorien mysqld[22611]: InnoDB: http://dev.mysql.com/ doc/mysql/en/Forcing_recovery.html
Feb 11 22:15:40 lorien mysqld[22611]: InnoDB: about forcing recovery. Feb 11 22:15:40 lorien mysqld[22611]: mysqld got signal 11;Feb 11 22:15:40 lorien mysqld[22611]: This could be because you hit a bug. It is also possible that this binary Feb 11 22:15:40 lorien mysqld[22611]: or one of the libraries it was linked against is corrupt, improperly built, Feb 11 22:15:40 lorien mysqld[22611]: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 11 22:15:40 lorien mysqld[22611]: We will try our best to scrape up some info that will hopefully help diagnose Feb 11 22:15:40 lorien mysqld[22611]: the problem, but since we have already crashed, something is definitely wrong
Feb 11 22:15:40 lorien mysqld[22611]: and this may fail. Feb 11 22:15:40 lorien mysqld[22611]: Feb 11 22:15:40 lorien mysqld[22611]: key_buffer_size=16777216 Feb 11 22:15:40 lorien mysqld[22611]: read_buffer_size=131072 Feb 11 22:15:40 lorien mysqld[22611]: max_used_connections=3 Feb 11 22:15:40 lorien mysqld[22611]: max_connections=100 Feb 11 22:15:40 lorien mysqld[22611]: threads_connected=3Feb 11 22:15:40 lorien mysqld[22611]: It is possible that mysqld could use up to Feb 11 22:15:40 lorien mysqld[22611]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
Feb 11 22:15:40 lorien mysqld[22611]: bytes of memoryFeb 11 22:15:40 lorien mysqld[22611]: Hope that's ok; if not, decrease some variables in the equation.
Feb 11 22:15:40 lorien mysqld[22611]: Feb 11 22:15:40 lorien mysqld[22611]: thd=0x8b23068Feb 11 22:15:40 lorien mysqld[22611]: Attempting backtrace. You can use the following information to find out Feb 11 22:15:40 lorien mysqld[22611]: where mysqld died. If you see no messages after this, something went
Feb 11 22:15:40 lorien mysqld[22611]: terribly wrong...Feb 11 22:15:40 lorien mysqld[22611]: Cannot determine thread, fp=0xb0c56aec, backtrace may not be correct. Feb 11 22:15:40 lorien mysqld[22611]: Stack range sanity check OK, backtrace follows:
Feb 11 22:15:40 lorien mysqld[22611]: 0x818f41c Feb 11 22:15:40 lorien mysqld[22611]: 0xffffe420 Feb 11 22:15:40 lorien mysqld[22611]: (nil) Feb 11 22:15:40 lorien mysqld[22611]: 0x8243f09 Feb 11 22:15:40 lorien mysqld[22611]: 0x81d90b5 Feb 11 22:15:40 lorien mysqld[22611]: 0x81d92ed Feb 11 22:15:40 lorien mysqld[22611]: 0x81e5424 Feb 11 22:15:40 lorien mysqld[22611]: 0x81e5eea Feb 11 22:15:40 lorien mysqld[22611]: 0x81ec708 Feb 11 22:15:40 lorien mysqld[22611]: 0x81ed010 Feb 11 22:15:40 lorien mysqld[22611]: 0x81a31a9 Feb 11 22:15:40 lorien mysqld[22611]: 0x81a899c Feb 11 22:15:40 lorien mysqld[22611]: 0x81a8fa6 Feb 11 22:15:40 lorien mysqld[22611]: 0x81aa128 Feb 11 22:15:40 lorien mysqld[22611]: 0x81aaa74 Feb 11 22:15:40 lorien mysqld[22611]: 0xb7fadcfd Feb 11 22:15:40 lorien mysqld[22611]: 0xb7def13eFeb 11 22:15:40 lorien mysqld[22611]: New value of fp=(nil) failed sanity check, terminating stack trace! Feb 11 22:15:40 lorien mysqld[22611]: Please read http:// dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved Feb 11 22:15:40 lorien mysqld[22611]: stack trace is much more helpful in diagnosing the problem, so please do
Feb 11 22:15:40 lorien mysqld[22611]: resolve it Feb 11 22:15:40 lorien mysqld[22611]: Trying to get some variables.Feb 11 22:15:40 lorien mysqld[22611]: Some pointers may be invalid and cause the dump to abort... Feb 11 22:15:40 lorien mysqld[22611]: thd->query at 0x8b461d0 = SELECT flag FROM bayes_seen
Feb 11 22:15:40 lorien mysqld[22611]: WHERE id = '2'Feb 11 22:15:40 lorien mysqld[22611]: AND msgid = '[EMAIL PROTECTED]'
Feb 11 22:15:40 lorien mysqld[22611]: thd->thread_id=5Feb 11 22:15:40 lorien mysqld[22611]: The manual page at http:// www.mysql.com/doc/en/Crashing.html contains Feb 11 22:15:40 lorien mysqld[22611]: information that should help you find out what is causing the crash. Feb 11 22:15:40 lorien mysqld_safe[25019]: Number of processes running now: 0
Feb 11 22:15:40 lorien mysqld_safe[25021]: restartedFeb 11 22:15:40 lorien mysqld[25024]: 060211 22:15:40 InnoDB: Database was not shut down normally!
Feb 11 22:15:40 lorien mysqld[25024]: InnoDB: Starting crash recovery.Feb 11 22:15:40 lorien mysqld[25024]: InnoDB: Reading tablespace information from the .ibd files... Feb 11 22:15:40 lorien mysqld[25024]: InnoDB: Restoring possible half- written data pages from the doublewrite
Feb 11 22:15:40 lorien mysqld[25024]: InnoDB: buffer...Feb 11 22:15:40 lorien mysqld[25024]: 060211 22:15:40 InnoDB: Starting log scan based on checkpoint at Feb 11 22:15:40 lorien mysqld[25024]: InnoDB: log sequence number 0 2010085433. Feb 11 22:15:40 lorien mysqld[25024]: InnoDB: Doing recovery: scanned up to log sequence number 0 2010085433 Feb 11 22:15:40 lorien mysqld[25024]: InnoDB: Last MySQL binlog file position 0 98, file name /var/log/mysql/mysql-bin.000899 Feb 11 22:15:40 lorien mysqld[25024]: 060211 22:15:40 InnoDB: Started; log sequence number 0 2010085433 Feb 11 22:15:40 lorien mysqld[25024]: 060211 22:15:40 [Note] Recovering after a crash using /var/log/mysql/mysql-bin Feb 11 22:15:40 lorien mysqld[25024]: 060211 22:15:40 [Note] Starting crash recovery... Feb 11 22:15:40 lorien mysqld[25024]: 060211 22:15:40 [Note] Crash recovery finished. Feb 11 22:15:41 lorien mysqld[25024]: 060211 22:15:41 [Note] /usr/ sbin/mysqld: ready for connections. Feb 11 22:15:41 lorien mysqld[25024]: Version: '5.0.18-Debian_7-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian Etch distribution Feb 12 00:51:42 lorien mysqld[25024]: 060212 0:51:42InnoDB: Assertion failure in thread 2965867440 in file row0mysql.c line 341 Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: Failing assertion: mbminlen == 1 Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: We intentionally generate a memory trap. Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: If you get repeated assertion failures or crashes, even Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: immediately after the mysqld startup, there may be Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: corruption in the InnoDB tablespace. Please refer to Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: http://dev.mysql.com/ doc/mysql/en/Forcing_recovery.html
Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: about forcing recovery. Feb 12 00:51:42 lorien mysqld[25024]: mysqld got signal 11;Feb 12 00:51:42 lorien mysqld[25024]: This could be because you hit a bug. It is also possible that this binary Feb 12 00:51:42 lorien mysqld[25024]: or one of the libraries it was linked against is corrupt, improperly built, Feb 12 00:51:42 lorien mysqld[25024]: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 12 00:51:42 lorien mysqld[25024]: We will try our best to scrape up some info that will hopefully help diagnose Feb 12 00:51:42 lorien mysqld[25024]: the problem, but since we have already crashed, something is definitely wrong
Feb 12 00:51:42 lorien mysqld[25024]: and this may fail. Feb 12 00:51:42 lorien mysqld[25024]: Feb 12 00:51:42 lorien mysqld[25024]: key_buffer_size=16777216 Feb 12 00:51:42 lorien mysqld[25024]: read_buffer_size=131072 Feb 12 00:51:42 lorien mysqld[25024]: max_used_connections=6 Feb 12 00:51:42 lorien mysqld[25024]: max_connections=100 Feb 12 00:51:42 lorien mysqld[25024]: threads_connected=6Feb 12 00:51:42 lorien mysqld[25024]: It is possible that mysqld could use up to Feb 12 00:51:42 lorien mysqld[25024]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
Feb 12 00:51:42 lorien mysqld[25024]: bytes of memoryFeb 12 00:51:42 lorien mysqld[25024]: Hope that's ok; if not, decrease some variables in the equation.
Feb 12 00:51:42 lorien mysqld[25024]: Feb 12 00:51:42 lorien mysqld[25024]: thd=0x8b27080Feb 12 00:51:42 lorien mysqld[25024]: Attempting backtrace. You can use the following information to find out Feb 12 00:51:42 lorien mysqld[25024]: where mysqld died. If you see no messages after this, something went
Feb 12 00:51:42 lorien mysqld[25024]: terribly wrong...Feb 12 00:51:42 lorien mysqld[25024]: Cannot determine thread, fp=0xb0c76aec, backtrace may not be correct. Feb 12 00:51:42 lorien mysqld[25024]: Stack range sanity check OK, backtrace follows:
Feb 12 00:51:42 lorien mysqld[25024]: 0x818f41c Feb 12 00:51:42 lorien mysqld[25024]: 0xffffe420 Feb 12 00:51:42 lorien mysqld[25024]: (nil) Feb 12 00:51:42 lorien mysqld[25024]: 0x8243f09 Feb 12 00:51:42 lorien mysqld[25024]: 0x81d90b5 Feb 12 00:51:42 lorien mysqld[25024]: 0x81d92ed Feb 12 00:51:42 lorien mysqld[25024]: 0x81e5424 Feb 12 00:51:42 lorien mysqld[25024]: 0x81e5eea Feb 12 00:51:42 lorien mysqld[25024]: 0x81ec708 Feb 12 00:51:42 lorien mysqld[25024]: 0x81ed010 Feb 12 00:51:42 lorien mysqld[25024]: 0x81a31a9 Feb 12 00:51:42 lorien mysqld[25024]: 0x81a899c Feb 12 00:51:42 lorien mysqld[25024]: 0x81a8fa6 Feb 12 00:51:42 lorien mysqld[25024]: 0x81aa128 Feb 12 00:51:42 lorien mysqld[25024]: 0x81aaa74 Feb 12 00:51:42 lorien mysqld[25024]: 0xb7fadcfd Feb 12 00:51:42 lorien mysqld[25024]: 0xb7def13eFeb 12 00:51:42 lorien mysqld[25024]: New value of fp=(nil) failed sanity check, terminating stack trace! Feb 12 00:51:42 lorien mysqld[25024]: Please read http:// dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved Feb 12 00:51:42 lorien mysqld[25024]: stack trace is much more helpful in diagnosing the problem, so please do
Feb 12 00:51:42 lorien mysqld[25024]: resolve it Feb 12 00:51:42 lorien mysqld[25024]: Trying to get some variables.Feb 12 00:51:42 lorien mysqld[25024]: Some pointers may be invalid and cause the dump to abort... Feb 12 00:51:42 lorien mysqld[25024]: thd->query at 0x8b2a7c8 = SELECT flag FROM bayes_seen
Feb 12 00:51:42 lorien mysqld[25024]: WHERE id = '2'Feb 12 00:51:42 lorien mysqld[25024]: AND msgid = '[EMAIL PROTECTED]'
Feb 12 00:51:42 lorien mysqld[25024]: thd->thread_id=32Feb 12 00:51:42 lorien mysqld[25024]: The manual page at http:// www.mysql.com/doc/en/Crashing.html contains Feb 12 00:51:42 lorien mysqld[25024]: information that should help you find out what is causing the crash. Feb 12 00:51:42 lorien mysqld[25024]: InnoDB: Thread 2991299504 stopped in file ./../include/sync0sync.ic line 111 Feb 12 00:51:42 lorien mysqld_safe[9891]: Number of processes running now: 0
Feb 12 00:51:42 lorien mysqld_safe[9893]: restartedFeb 12 00:51:43 lorien mysqld[9896]: 060212 0:51:43 InnoDB: Database was not shut down normally!
Feb 12 00:51:43 lorien mysqld[9896]: InnoDB: Starting crash recovery.Feb 12 00:51:43 lorien mysqld[9896]: InnoDB: Reading tablespace information from the .ibd files... Feb 12 00:51:43 lorien mysqld[9896]: InnoDB: Restoring possible half- written data pages from the doublewrite
Feb 12 00:51:43 lorien mysqld[9896]: InnoDB: buffer...Feb 12 00:51:44 lorien mysqld[9896]: 060212 0:51:44 InnoDB: Starting log scan based on checkpoint at Feb 12 00:51:44 lorien mysqld[9896]: InnoDB: log sequence number 0 2010165650. Feb 12 00:51:44 lorien mysqld[9896]: InnoDB: Doing recovery: scanned up to log sequence number 0 2010168586 Feb 12 00:51:44 lorien mysqld[9896]: 060212 0:51:44 InnoDB: Starting an apply batch of log records to the database... Feb 12 00:51:44 lorien mysqld[9896]: InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
Feb 12 00:51:44 lorien mysqld[9896]: InnoDB: Apply batch completedFeb 12 00:51:44 lorien mysqld[9896]: InnoDB: Last MySQL binlog file position 0 98, file name /var/log/mysql/mysql-bin.000900 Feb 12 00:51:44 lorien mysqld[9896]: 060212 0:51:44 InnoDB: Started; log sequence number 0 2010168586 Feb 12 00:51:44 lorien mysqld[9896]: 060212 0:51:44 [Note] Recovering after a crash using /var/log/mysql/mysql-bin Feb 12 00:51:44 lorien mysqld[9896]: 060212 0:51:44 [Note] Starting crash recovery... Feb 12 00:51:44 lorien mysqld[9896]: 060212 0:51:44 [Note] Crash recovery finished. Feb 12 00:51:45 lorien mysqld[9896]: 060212 0:51:45 [Note] /usr/sbin/ mysqld: ready for connections. Feb 12 00:51:45 lorien mysqld[9896]: Version: '5.0.18-Debian_7-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian Etch distribution
Thanks, -- -Jamie L. Penman-Smithson <[EMAIL PROTECTED]> t: +44 1273 424795; f: +44 1273 424795 PGP: C0A7 955E EED6 A309 23D7 863B C76A 26A3 F0DC FCA8 never send mail to: [EMAIL PROTECTED]
PGP.sig
Description: This is a digitally signed message part
