120223 06:54:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 120223 6:54:36 InnoDB: Initializing buffer pool, size = 8.0M 120223 6:54:36 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 120223 6:54:36 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 120223 6:54:37 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 120223 6:54:37 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 120223 6:54:37 InnoDB: Started; log sequence number 0 0 120223 6:54:37 [Note] Event Scheduler: Loaded 0 events 120223 6:54:37 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.61' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 120302 21:42:23 [Note] /usr/libexec/mysqld: Normal shutdown 120302 21:42:23 [Note] Event Scheduler: Purging the queue. 0 events 120302 21:42:23 InnoDB: Starting shutdown... 120302 21:42:28 InnoDB: Shutdown completed; log sequence number 0 44233 120302 21:42:28 [Note] /usr/libexec/mysqld: Shutdown complete 120302 21:42:28 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 120302 21:42:51 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 120302 21:42:51 InnoDB: Initializing buffer pool, size = 8.0M 120302 21:42:51 InnoDB: Completed initialization of buffer pool 120302 21:42:51 InnoDB: Started; log sequence number 0 44233 120302 21:42:51 [Note] Event Scheduler: Loaded 0 events 120302 21:42:51 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.61' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 121130 11:58:56 [Note] /usr/libexec/mysqld: Normal shutdown 121130 11:58:56 [Note] Event Scheduler: Purging the queue. 0 events 121130 11:58:56 InnoDB: Starting shutdown... 121130 11:58:57 InnoDB: Shutdown completed; log sequence number 0 44233 121130 11:58:57 [Note] /usr/libexec/mysqld: Shutdown complete 121130 11:58:57 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 121204 19:36:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 121204 19:36:15 InnoDB: Initializing buffer pool, size = 8.0M 121204 19:36:15 InnoDB: Completed initialization of buffer pool 121204 19:36:15 InnoDB: Started; log sequence number 0 44233 121204 19:36:15 [Note] Event Scheduler: Loaded 0 events 121204 19:36:15 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.61' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 121204 19:47:31 [Note] /usr/libexec/mysqld: Normal shutdown 121204 19:47:31 [Note] Event Scheduler: Purging the queue. 0 events 121204 19:47:31 InnoDB: Starting shutdown... 121204 19:47:31 InnoDB: Shutdown completed; log sequence number 0 44233 121204 19:47:31 [Note] /usr/libexec/mysqld: Shutdown complete 121204 19:47:31 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 121205 13:00:22 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 121205 13:00:22 InnoDB: Initializing buffer pool, size = 8.0M 121205 13:00:22 InnoDB: Completed initialization of buffer pool 121205 13:00:23 InnoDB: Started; log sequence number 0 44233 121205 13:00:23 [Note] Event Scheduler: Loaded 0 events 121205 13:00:23 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.61' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 121205 13:09:33 [Note] /usr/libexec/mysqld: Normal shutdown 121205 13:09:33 [Note] Event Scheduler: Purging the queue. 0 events 121205 13:09:33 InnoDB: Starting shutdown... 121205 13:09:35 InnoDB: Shutdown completed; log sequence number 0 44233 121205 13:09:35 [Note] /usr/libexec/mysqld: Shutdown complete 121205 13:09:35 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 121205 13:09:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 121205 13:09:36 InnoDB: Initializing buffer pool, size = 8.0M 121205 13:09:36 InnoDB: Completed initialization of buffer pool 121205 13:09:36 InnoDB: Started; log sequence number 0 44233 121205 13:09:36 [Note] Event Scheduler: Loaded 0 events 121205 13:09:36 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.66' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 121205 13:10:49 [Note] /usr/libexec/mysqld: Normal shutdown 121205 13:10:49 [Note] Event Scheduler: Purging the queue. 0 events 121205 13:10:49 InnoDB: Starting shutdown... 121205 13:10:52 InnoDB: Shutdown completed; log sequence number 0 44233 121205 13:10:52 [Note] /usr/libexec/mysqld: Shutdown complete 121205 13:10:52 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 121205 13:11:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 121205 13:11:14 InnoDB: Initializing buffer pool, size = 8.0M 121205 13:11:14 InnoDB: Completed initialization of buffer pool 121205 13:11:14 InnoDB: Started; log sequence number 0 44233 121205 13:11:14 [Note] Event Scheduler: Loaded 0 events 121205 13:11:14 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.66' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 121205 13:31:44 [Note] /usr/libexec/mysqld: Normal shutdown 121205 13:31:44 [Note] Event Scheduler: Purging the queue. 0 events 121205 13:31:44 InnoDB: Starting shutdown... 121205 13:31:45 InnoDB: Shutdown completed; log sequence number 0 44233 121205 13:31:45 [Note] /usr/libexec/mysqld: Shutdown complete 121205 13:31:45 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 121205 13:33:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 121205 13:33:47 InnoDB: Initializing buffer pool, size = 8.0M 121205 13:33:47 InnoDB: Completed initialization of buffer pool 121205 13:33:47 InnoDB: Started; log sequence number 0 44233 121205 13:33:47 [Note] Event Scheduler: Loaded 0 events 121205 13:33:47 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.66' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 121213 9:14:07 [Note] /usr/libexec/mysqld: Normal shutdown 121213 9:14:07 [Note] Event Scheduler: Purging the queue. 0 events 121213 9:14:07 InnoDB: Starting shutdown... 121213 9:14:08 InnoDB: Shutdown completed; log sequence number 0 44233 121213 9:14:08 [Note] /usr/libexec/mysqld: Shutdown complete 121213 09:14:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 121213 09:19:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 121213 9:19:03 InnoDB: Initializing buffer pool, size = 8.0M 121213 9:19:03 InnoDB: Completed initialization of buffer pool 121213 9:19:03 InnoDB: Started; log sequence number 0 44233 121213 9:19:04 [Note] Event Scheduler: Loaded 0 events 121213 9:19:04 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.66' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130201 16:40:06 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130201 16:40:07 InnoDB: Initializing buffer pool, size = 8.0M 130201 16:40:07 InnoDB: Completed initialization of buffer pool 130201 16:40:07 InnoDB: Started; log sequence number 0 44233 130201 16:40:07 [Note] Event Scheduler: Loaded 0 events 130201 16:40:07 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.66' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130218 23:25:14 [Note] /usr/libexec/mysqld: Normal shutdown 130218 23:25:14 [Note] Event Scheduler: Purging the queue. 0 events 130218 23:25:14 InnoDB: Starting shutdown... 130218 23:25:16 InnoDB: Shutdown completed; log sequence number 0 44233 130218 23:25:16 [Note] /usr/libexec/mysqld: Shutdown complete 130218 23:25:16 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130218 23:25:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130218 23:25:17 InnoDB: Initializing buffer pool, size = 8.0M 130218 23:25:17 InnoDB: Completed initialization of buffer pool 130218 23:25:17 InnoDB: Started; log sequence number 0 44233 130218 23:25:17 [Note] Event Scheduler: Loaded 0 events 130218 23:25:17 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130218 23:37:14 [Note] /usr/libexec/mysqld: Normal shutdown 130218 23:37:14 [Note] Event Scheduler: Purging the queue. 0 events 130218 23:37:14 InnoDB: Starting shutdown... 130218 23:37:18 InnoDB: Shutdown completed; log sequence number 0 44233 130218 23:37:18 [Note] /usr/libexec/mysqld: Shutdown complete 130218 23:37:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130218 23:37:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130218 23:37:48 InnoDB: Initializing buffer pool, size = 8.0M 130218 23:37:48 InnoDB: Completed initialization of buffer pool 130218 23:37:48 InnoDB: Started; log sequence number 0 44233 130218 23:37:48 [Note] Event Scheduler: Loaded 0 events 130218 23:37:48 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130219 13:53:40 [Note] /usr/libexec/mysqld: Normal shutdown 130219 13:53:40 [Note] Event Scheduler: Purging the queue. 0 events 130219 13:53:40 InnoDB: Starting shutdown... 130219 13:53:42 InnoDB: Shutdown completed; log sequence number 0 705479 130219 13:53:42 [Note] /usr/libexec/mysqld: Shutdown complete 130219 13:53:42 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130219 13:54:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130219 13:54:10 InnoDB: Initializing buffer pool, size = 8.0M 130219 13:54:10 InnoDB: Completed initialization of buffer pool 130219 13:54:11 InnoDB: Started; log sequence number 0 705479 130219 13:54:11 [Note] Event Scheduler: Loaded 0 events 130219 13:54:11 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130219 15:00:35 [Note] /usr/libexec/mysqld: Normal shutdown 130219 15:00:35 [Note] Event Scheduler: Purging the queue. 0 events 130219 15:00:35 InnoDB: Starting shutdown... 130219 15:00:40 InnoDB: Shutdown completed; log sequence number 0 119466395 130219 15:00:40 [Note] /usr/libexec/mysqld: Shutdown complete 130219 15:00:40 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130219 15:01:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130219 15:01:54 InnoDB: Initializing buffer pool, size = 8.0M 130219 15:01:54 InnoDB: Completed initialization of buffer pool 130219 15:01:54 InnoDB: Started; log sequence number 0 119466395 130219 15:01:54 [Note] Event Scheduler: Loaded 0 events 130219 15:01:54 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130219 15:03:04 [Note] /usr/libexec/mysqld: Normal shutdown 130219 15:03:04 [Note] Event Scheduler: Purging the queue. 0 events 130219 15:03:04 InnoDB: Starting shutdown... 130219 15:03:06 InnoDB: Shutdown completed; log sequence number 0 119470011 130219 15:03:06 [Note] /usr/libexec/mysqld: Shutdown complete 130219 15:03:06 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130219 15:03:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130219 15:03:58 InnoDB: Initializing buffer pool, size = 8.0M 130219 15:03:58 InnoDB: Completed initialization of buffer pool 130219 15:03:58 InnoDB: Started; log sequence number 0 119470011 130219 15:03:58 [Note] Event Scheduler: Loaded 0 events 130219 15:03:58 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130220 10:07:24 [Note] /usr/libexec/mysqld: Normal shutdown 130220 10:07:24 [Note] Event Scheduler: Purging the queue. 0 events 130220 10:07:24 InnoDB: Starting shutdown... 130220 10:07:26 InnoDB: Shutdown completed; log sequence number 0 728053695 130220 10:07:26 [Note] /usr/libexec/mysqld: Shutdown complete 130220 10:07:26 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130220 10:08:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130220 10:08:01 InnoDB: Initializing buffer pool, size = 8.0M 130220 10:08:01 InnoDB: Completed initialization of buffer pool 130220 10:08:01 InnoDB: Started; log sequence number 0 728053695 130220 10:08:01 [Note] Event Scheduler: Loaded 0 events 130220 10:08:01 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130301 12:12:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130301 12:12:54 InnoDB: Initializing buffer pool, size = 8.0M 130301 12:12:54 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 820267709 130301 12:12:54 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 820268299 130301 12:12:55 InnoDB: Error: page 32770 log sequence number 0 820691676 InnoDB: is in the future! Current system log sequence number 0 820268299. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130301 12:12:55 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130301 12:12:56 InnoDB: Started; log sequence number 0 820268299 130301 12:12:56 [Note] Event Scheduler: Loaded 0 events 130301 12:12:56 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130301 12:13:29 InnoDB: Error: page 32768 log sequence number 0 820676685 InnoDB: is in the future! Current system log sequence number 0 820270351. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130301 12:13:30 InnoDB: Error: page 11226 log sequence number 0 820396457 InnoDB: is in the future! Current system log sequence number 0 820283887. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130301 12:13:31 InnoDB: Error: page 11227 log sequence number 0 820397315 InnoDB: is in the future! Current system log sequence number 0 820284748. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130301 12:13:31 InnoDB: Error: page 11262 log sequence number 0 820392189 InnoDB: is in the future! Current system log sequence number 0 820284748. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 14:02:43 [Note] /usr/libexec/mysqld: Normal shutdown 130309 14:02:43 [Note] Event Scheduler: Purging the queue. 0 events 130309 14:02:44 InnoDB: Starting shutdown... 130309 14:02:48 InnoDB: Shutdown completed; log sequence number 0 890612047 130309 14:02:49 [Note] /usr/libexec/mysqld: Shutdown complete 130309 14:02:49 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 14:21:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 14:21:34 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:21:34 InnoDB: Completed initialization of buffer pool 130309 14:21:35 InnoDB: Started; log sequence number 0 890612047 130309 14:21:35 [Note] Event Scheduler: Loaded 0 events 130309 14:21:35 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:21:36 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168027! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3954026158 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:22:20 InnoDB: Assertion failure in thread 140311774869248 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:22:20 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=11 max_threads=151 thread_count=11 connection_count=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f9ceef56500] /lib64/libc.so.6(gsignal+0x35) [0x7f9ced5e58a5] /lib64/libc.so.6(abort+0x175) [0x7f9ced5e7085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f9ceef4e851] /lib64/libc.so.6(clone+0x6d) [0x7f9ced69b90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:22:20 mysqld_safe Number of processes running now: 0 130309 14:22:20 mysqld_safe mysqld restarted 130309 14:22:21 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:22:21 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 890612047 130309 14:22:21 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 130309 14:22:21 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:22:22 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed InnoDB: Doing recovery: scanned up to log sequence number 0 892772259 130309 14:22:22 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:22:23 InnoDB: Started; log sequence number 0 892772259 130309 14:22:23 [Note] Event Scheduler: Loaded 0 events 130309 14:22:23 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:22:24 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168032! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 714201849 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:22:38 InnoDB: Assertion failure in thread 140002470115072 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:22:38 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f54eaf2b500] /lib64/libc.so.6(gsignal+0x35) [0x7f54e95ba8a5] /lib64/libc.so.6(abort+0x175) [0x7f54e95bc085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f54eaf23851] /lib64/libc.so.6(clone+0x6d) [0x7f54e967090d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:22:38 mysqld_safe Number of processes running now: 0 130309 14:22:38 mysqld_safe mysqld restarted 130309 14:22:38 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:22:38 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892772259 130309 14:22:38 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892778377 130309 14:22:38 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:22:39 InnoDB: Started; log sequence number 0 892778377 130309 14:22:39 [Note] Event Scheduler: Loaded 0 events 130309 14:22:39 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:22:40 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168035! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:22:53 InnoDB: Assertion failure in thread 140129750480640 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:22:53 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f72917e3500] /lib64/libc.so.6(gsignal+0x35) [0x7f728fe728a5] /lib64/libc.so.6(abort+0x175) [0x7f728fe74085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f72917db851] /lib64/libc.so.6(clone+0x6d) [0x7f728ff2890d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:22:53 mysqld_safe Number of processes running now: 0 130309 14:22:53 mysqld_safe mysqld restarted 130309 14:22:53 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:22:53 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892778377 130309 14:22:53 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892779337 130309 14:22:53 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:22:54 InnoDB: Started; log sequence number 0 892779337 130309 14:22:54 [Note] Event Scheduler: Loaded 0 events 130309 14:22:54 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:22:55 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168038! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:23:08 InnoDB: Assertion failure in thread 140291942115072 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:23:08 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=4 max_threads=151 thread_count=4 connection_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f9854ec9500] /lib64/libc.so.6(gsignal+0x35) [0x7f98535588a5] /lib64/libc.so.6(abort+0x175) [0x7f985355a085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f9854ec1851] /lib64/libc.so.6(clone+0x6d) [0x7f985360e90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:23:08 mysqld_safe Number of processes running now: 0 130309 14:23:08 mysqld_safe mysqld restarted 130309 14:23:08 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:23:08 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892779337 130309 14:23:08 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892780298 130309 14:23:08 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:23:09 InnoDB: Started; log sequence number 0 892780298 130309 14:23:09 [Note] Event Scheduler: Loaded 0 events 130309 14:23:09 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:23:10 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168041! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:23:23 InnoDB: Assertion failure in thread 139753450100480 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:23:23 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f1af3e59500] /lib64/libc.so.6(gsignal+0x35) [0x7f1af24e88a5] /lib64/libc.so.6(abort+0x175) [0x7f1af24ea085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f1af3e51851] /lib64/libc.so.6(clone+0x6d) [0x7f1af259e90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:23:23 mysqld_safe Number of processes running now: 0 130309 14:23:23 mysqld_safe mysqld restarted 130309 14:23:23 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:23:23 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892780298 130309 14:23:23 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892781258 130309 14:23:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:23:24 InnoDB: Started; log sequence number 0 892781258 130309 14:23:24 [Note] Event Scheduler: Loaded 0 events 130309 14:23:24 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:23:25 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168044! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:23:38 InnoDB: Assertion failure in thread 140661737105152 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:23:38 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fee694b0500] /lib64/libc.so.6(gsignal+0x35) [0x7fee67b3f8a5] /lib64/libc.so.6(abort+0x175) [0x7fee67b41085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fee694a8851] /lib64/libc.so.6(clone+0x6d) [0x7fee67bf590d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:23:39 mysqld_safe Number of processes running now: 0 130309 14:23:39 mysqld_safe mysqld restarted 130309 14:23:39 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:23:39 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892781258 130309 14:23:39 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892782218 130309 14:23:39 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:23:39 InnoDB: Started; log sequence number 0 892782218 130309 14:23:39 [Note] Event Scheduler: Loaded 0 events 130309 14:23:39 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:23:40 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168047! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:23:54 InnoDB: Assertion failure in thread 139690039904000 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:23:54 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f0c2b9ec500] /lib64/libc.so.6(gsignal+0x35) [0x7f0c2a07b8a5] /lib64/libc.so.6(abort+0x175) [0x7f0c2a07d085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f0c2b9e4851] /lib64/libc.so.6(clone+0x6d) [0x7f0c2a13190d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:23:54 mysqld_safe Number of processes running now: 0 130309 14:23:54 mysqld_safe mysqld restarted 130309 14:23:54 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:23:54 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892782218 130309 14:23:54 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892783178 130309 14:23:54 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:23:55 InnoDB: Started; log sequence number 0 892783178 130309 14:23:55 [Note] Event Scheduler: Loaded 0 events 130309 14:23:55 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:23:56 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168050! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:24:09 InnoDB: Assertion failure in thread 139974515181312 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:24:09 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=4 max_threads=151 thread_count=4 connection_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f4e67a94500] /lib64/libc.so.6(gsignal+0x35) [0x7f4e661238a5] /lib64/libc.so.6(abort+0x175) [0x7f4e66125085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f4e67a8c851] /lib64/libc.so.6(clone+0x6d) [0x7f4e661d990d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:24:09 mysqld_safe Number of processes running now: 0 130309 14:24:09 mysqld_safe mysqld restarted 130309 14:24:09 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:24:09 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892783178 130309 14:24:09 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892784122 130309 14:24:09 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:24:10 InnoDB: Started; log sequence number 0 892784122 130309 14:24:10 [Note] Event Scheduler: Loaded 0 events 130309 14:24:10 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:24:11 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168053! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:24:24 InnoDB: Assertion failure in thread 140038765520640 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:24:24 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f5d5d4a3500] /lib64/libc.so.6(gsignal+0x35) [0x7f5d5bb328a5] /lib64/libc.so.6(abort+0x175) [0x7f5d5bb34085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f5d5d49b851] /lib64/libc.so.6(clone+0x6d) [0x7f5d5bbe890d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:24:24 mysqld_safe Number of processes running now: 0 130309 14:24:24 mysqld_safe mysqld restarted 130309 14:24:24 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:24:24 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892784122 130309 14:24:24 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892785082 130309 14:24:24 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:24:25 InnoDB: Started; log sequence number 0 892785082 130309 14:24:25 [Note] Event Scheduler: Loaded 0 events 130309 14:24:25 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:24:26 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168056! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:24:39 InnoDB: Assertion failure in thread 139760368563968 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:24:39 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f1c8c1cb500] /lib64/libc.so.6(gsignal+0x35) [0x7f1c8a85a8a5] /lib64/libc.so.6(abort+0x175) [0x7f1c8a85c085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f1c8c1c3851] /lib64/libc.so.6(clone+0x6d) [0x7f1c8a91090d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:24:39 mysqld_safe Number of processes running now: 0 130309 14:24:39 mysqld_safe mysqld restarted 130309 14:24:39 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:24:39 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892785082 130309 14:24:39 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892786042 130309 14:24:39 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:24:40 InnoDB: Started; log sequence number 0 892786042 130309 14:24:40 [Note] Event Scheduler: Loaded 0 events 130309 14:24:40 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:24:41 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168059! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:24:54 InnoDB: Assertion failure in thread 140242854065920 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:24:54 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f8ce1f02500] /lib64/libc.so.6(gsignal+0x35) [0x7f8ce05918a5] /lib64/libc.so.6(abort+0x175) [0x7f8ce0593085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f8ce1efa851] /lib64/libc.so.6(clone+0x6d) [0x7f8ce064790d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:24:54 mysqld_safe Number of processes running now: 0 130309 14:24:54 mysqld_safe mysqld restarted 130309 14:24:54 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:24:54 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892786042 130309 14:24:54 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892787002 130309 14:24:54 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:24:55 InnoDB: Started; log sequence number 0 892787002 130309 14:24:55 [Note] Event Scheduler: Loaded 0 events 130309 14:24:55 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:24:56 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168062! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:25:09 InnoDB: Assertion failure in thread 139932708366080 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:25:09 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=5 max_threads=151 thread_count=5 connection_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f44b0c1a500] /lib64/libc.so.6(gsignal+0x35) [0x7f44af2a98a5] /lib64/libc.so.6(abort+0x175) [0x7f44af2ab085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f44b0c12851] /lib64/libc.so.6(clone+0x6d) [0x7f44af35f90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:25:09 mysqld_safe Number of processes running now: 0 130309 14:25:09 mysqld_safe mysqld restarted 130309 14:25:09 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:25:10 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892787002 130309 14:25:10 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892787962 130309 14:25:10 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:25:10 InnoDB: Started; log sequence number 0 892787962 130309 14:25:10 [Note] Event Scheduler: Loaded 0 events 130309 14:25:10 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:25:11 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168065! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:25:25 InnoDB: Assertion failure in thread 140111667250944 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:25:25 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f6e57303500] /lib64/libc.so.6(gsignal+0x35) [0x7f6e559928a5] /lib64/libc.so.6(abort+0x175) [0x7f6e55994085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f6e572fb851] /lib64/libc.so.6(clone+0x6d) [0x7f6e55a4890d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:25:25 mysqld_safe Number of processes running now: 0 130309 14:25:25 mysqld_safe mysqld restarted 130309 14:25:25 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:25:25 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892787962 130309 14:25:25 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892788922 130309 14:25:25 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:25:25 InnoDB: Started; log sequence number 0 892788922 130309 14:25:25 [Note] Event Scheduler: Loaded 0 events 130309 14:25:25 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:25:26 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168068! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:25:40 InnoDB: Assertion failure in thread 140419742541568 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:25:40 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fb61231b500] /lib64/libc.so.6(gsignal+0x35) [0x7fb6109aa8a5] /lib64/libc.so.6(abort+0x175) [0x7fb6109ac085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fb612313851] /lib64/libc.so.6(clone+0x6d) [0x7fb610a6090d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:25:40 mysqld_safe Number of processes running now: 0 130309 14:25:40 mysqld_safe mysqld restarted 130309 14:25:42 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:25:42 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892788922 130309 14:25:42 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892789883 130309 14:25:42 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:25:42 InnoDB: Started; log sequence number 0 892789883 130309 14:25:42 [Note] Event Scheduler: Loaded 0 events 130309 14:25:42 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:25:52 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168073! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1342085593 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:26:04 InnoDB: Assertion failure in thread 140730834085632 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:26:04 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=8 max_threads=151 thread_count=8 connection_count=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7ffe848de500] /lib64/libc.so.6(gsignal+0x35) [0x7ffe82f6d8a5] /lib64/libc.so.6(abort+0x175) [0x7ffe82f6f085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7ffe848d6851] /lib64/libc.so.6(clone+0x6d) [0x7ffe8302390d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:26:04 mysqld_safe Number of processes running now: 0 130309 14:26:04 mysqld_safe mysqld restarted 130309 14:26:04 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:26:04 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892790493 130309 14:26:04 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892791488 130309 14:26:04 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:26:04 InnoDB: Started; log sequence number 0 892791488 130309 14:26:04 [Note] Event Scheduler: Loaded 0 events 130309 14:26:04 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:26:05 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168076! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:26:20 InnoDB: Assertion failure in thread 139854516238080 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:26:20 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f3277c8e500] /lib64/libc.so.6(gsignal+0x35) [0x7f327631d8a5] /lib64/libc.so.6(abort+0x175) [0x7f327631f085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f3277c86851] /lib64/libc.so.6(clone+0x6d) [0x7f32763d390d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:26:20 mysqld_safe Number of processes running now: 0 130309 14:26:20 mysqld_safe mysqld restarted 130309 14:26:20 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:26:20 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892791488 130309 14:26:20 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892793258 130309 14:26:20 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:26:20 InnoDB: Started; log sequence number 0 892793258 130309 14:26:20 [Note] Event Scheduler: Loaded 0 events 130309 14:26:20 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:26:21 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168079! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:26:35 InnoDB: Assertion failure in thread 140532240246528 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:26:35 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=7 max_threads=151 thread_count=7 connection_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fd0434a9500] /lib64/libc.so.6(gsignal+0x35) [0x7fd041b388a5] /lib64/libc.so.6(abort+0x175) [0x7fd041b3a085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fd0434a1851] /lib64/libc.so.6(clone+0x6d) [0x7fd041bee90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:26:35 mysqld_safe Number of processes running now: 0 130309 14:26:35 mysqld_safe mysqld restarted 130309 14:26:35 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:26:35 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892793258 130309 14:26:35 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892794218 130309 14:26:35 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:26:36 InnoDB: Started; log sequence number 0 892794218 130309 14:26:36 [Note] Event Scheduler: Loaded 0 events 130309 14:26:36 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:26:37 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168082! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:26:50 InnoDB: Assertion failure in thread 140498234763008 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:26:50 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fc85cc30500] /lib64/libc.so.6(gsignal+0x35) [0x7fc85b2bf8a5] /lib64/libc.so.6(abort+0x175) [0x7fc85b2c1085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fc85cc28851] /lib64/libc.so.6(clone+0x6d) [0x7fc85b37590d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:26:50 mysqld_safe Number of processes running now: 0 130309 14:26:50 mysqld_safe mysqld restarted 130309 14:26:50 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:26:50 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892794218 130309 14:26:50 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892795178 130309 14:26:50 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:26:51 InnoDB: Started; log sequence number 0 892795178 130309 14:26:51 [Note] Event Scheduler: Loaded 0 events 130309 14:26:51 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:26:52 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168085! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:27:06 InnoDB: Assertion failure in thread 140317789517568 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:27:06 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f9e59376500] /lib64/libc.so.6(gsignal+0x35) [0x7f9e57a058a5] /lib64/libc.so.6(abort+0x175) [0x7f9e57a07085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f9e5936e851] /lib64/libc.so.6(clone+0x6d) [0x7f9e57abb90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:27:06 mysqld_safe Number of processes running now: 0 130309 14:27:06 mysqld_safe mysqld restarted 130309 14:27:06 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:27:06 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892795178 130309 14:27:06 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892796138 130309 14:27:06 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:27:06 InnoDB: Started; log sequence number 0 892796138 130309 14:27:06 [Note] Event Scheduler: Loaded 0 events 130309 14:27:06 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:27:07 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168088! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:27:21 InnoDB: Assertion failure in thread 140493983807232 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:27:21 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fc75a6a9500] /lib64/libc.so.6(gsignal+0x35) [0x7fc758d388a5] /lib64/libc.so.6(abort+0x175) [0x7fc758d3a085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fc75a6a1851] /lib64/libc.so.6(clone+0x6d) [0x7fc758dee90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:27:21 mysqld_safe Number of processes running now: 0 130309 14:27:21 mysqld_safe mysqld restarted 130309 14:27:21 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:27:21 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892796138 130309 14:27:21 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892797098 130309 14:27:21 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:27:21 InnoDB: Started; log sequence number 0 892797098 130309 14:27:21 [Note] Event Scheduler: Loaded 0 events 130309 14:27:21 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:27:22 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168091! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:27:36 InnoDB: Assertion failure in thread 139830604314368 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:27:36 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f2ce6169500] /lib64/libc.so.6(gsignal+0x35) [0x7f2ce47f88a5] /lib64/libc.so.6(abort+0x175) [0x7f2ce47fa085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f2ce6161851] /lib64/libc.so.6(clone+0x6d) [0x7f2ce48ae90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:27:36 mysqld_safe Number of processes running now: 0 130309 14:27:36 mysqld_safe mysqld restarted 130309 14:27:36 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:27:36 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892797098 130309 14:27:36 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892798058 130309 14:27:36 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:27:37 InnoDB: Started; log sequence number 0 892798058 130309 14:27:37 [Note] Event Scheduler: Loaded 0 events 130309 14:27:37 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:27:38 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168094! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:27:51 InnoDB: Assertion failure in thread 140685383726848 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:27:51 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7ff3eb611500] /lib64/libc.so.6(gsignal+0x35) [0x7ff3e9ca08a5] /lib64/libc.so.6(abort+0x175) [0x7ff3e9ca2085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7ff3eb609851] /lib64/libc.so.6(clone+0x6d) [0x7ff3e9d5690d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:27:51 mysqld_safe Number of processes running now: 0 130309 14:27:51 mysqld_safe mysqld restarted 130309 14:27:51 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:27:51 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892798058 130309 14:27:51 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892799018 130309 14:27:51 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:27:52 InnoDB: Started; log sequence number 0 892799018 130309 14:27:52 [Note] Event Scheduler: Loaded 0 events 130309 14:27:52 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:27:53 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168097! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:28:06 InnoDB: Assertion failure in thread 140080022812416 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:28:06 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=5 max_threads=151 thread_count=5 connection_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f66fd93a500] /lib64/libc.so.6(gsignal+0x35) [0x7f66fbfc98a5] /lib64/libc.so.6(abort+0x175) [0x7f66fbfcb085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f66fd932851] /lib64/libc.so.6(clone+0x6d) [0x7f66fc07f90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:28:06 mysqld_safe Number of processes running now: 0 130309 14:28:06 mysqld_safe mysqld restarted 130309 14:28:06 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:28:06 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892799018 130309 14:28:06 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892799963 130309 14:28:06 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:28:07 InnoDB: Started; log sequence number 0 892799963 130309 14:28:07 [Note] Event Scheduler: Loaded 0 events 130309 14:28:07 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:28:08 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168100! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:28:21 InnoDB: Assertion failure in thread 140571106531072 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:28:21 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fd94ff64500] /lib64/libc.so.6(gsignal+0x35) [0x7fd94e5f38a5] /lib64/libc.so.6(abort+0x175) [0x7fd94e5f5085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fd94ff5c851] /lib64/libc.so.6(clone+0x6d) [0x7fd94e6a990d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:28:21 mysqld_safe Number of processes running now: 0 130309 14:28:21 mysqld_safe mysqld restarted 130309 14:28:22 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:28:22 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892799963 130309 14:28:22 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892800923 130309 14:28:22 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:28:22 InnoDB: Started; log sequence number 0 892800923 130309 14:28:22 [Note] Event Scheduler: Loaded 0 events 130309 14:28:22 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:28:23 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168103! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:28:36 InnoDB: Assertion failure in thread 140498668836608 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:28:36 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fc871bef500] /lib64/libc.so.6(gsignal+0x35) [0x7fc87027e8a5] /lib64/libc.so.6(abort+0x175) [0x7fc870280085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fc871be7851] /lib64/libc.so.6(clone+0x6d) [0x7fc87033490d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:28:36 mysqld_safe Number of processes running now: 0 130309 14:28:36 mysqld_safe mysqld restarted 130309 14:28:37 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:28:37 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892800923 130309 14:28:37 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892801883 130309 14:28:37 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:28:37 InnoDB: Started; log sequence number 0 892801883 130309 14:28:37 [Note] Event Scheduler: Loaded 0 events 130309 14:28:37 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:28:38 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168106! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:28:52 InnoDB: Assertion failure in thread 139700364982016 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:28:52 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=4 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f0e93a9d500] /lib64/libc.so.6(gsignal+0x35) [0x7f0e9212c8a5] /lib64/libc.so.6(abort+0x175) [0x7f0e9212e085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f0e93a95851] /lib64/libc.so.6(clone+0x6d) [0x7f0e921e290d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:28:52 mysqld_safe Number of processes running now: 0 130309 14:28:52 mysqld_safe mysqld restarted 130309 14:28:52 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:28:52 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892801883 130309 14:28:52 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892802535 130309 14:28:52 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:28:52 InnoDB: Started; log sequence number 0 892802535 130309 14:28:52 [Note] Event Scheduler: Loaded 0 events 130309 14:28:52 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:28:53 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168108! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com 130309 14:32:04 [Note] /usr/libexec/mysqld: Normal shutdown 130309 14:32:04 [Note] Event Scheduler: Purging the queue. 0 events 130309 14:32:04 InnoDB: Starting shutdown... 130309 14:32:08 InnoDB: Shutdown completed; log sequence number 0 892802535 130309 14:32:08 [Note] /usr/libexec/mysqld: Shutdown complete 130309 14:32:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 14:33:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 14:33:12 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:33:12 InnoDB: Completed initialization of buffer pool 130309 14:33:12 InnoDB: Started; log sequence number 0 892802535 130309 14:33:12 [Note] Event Scheduler: Loaded 0 events 130309 14:33:12 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:33:13 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168108! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:44:48 InnoDB: Assertion failure in thread 140334411536128 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:44:48 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=11 max_threads=151 thread_count=11 connection_count=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fa2386c1500] /lib64/libc.so.6(gsignal+0x35) [0x7fa236d508a5] /lib64/libc.so.6(abort+0x175) [0x7fa236d52085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fa2386b9851] /lib64/libc.so.6(clone+0x6d) [0x7fa236e0690d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:44:48 mysqld_safe Number of processes running now: 0 130309 14:44:48 mysqld_safe mysqld restarted 130309 14:44:48 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:44:48 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892802535 130309 14:44:48 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892803710 130309 14:44:48 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:44:49 InnoDB: Started; log sequence number 0 892803710 130309 14:44:49 [Note] Event Scheduler: Loaded 0 events 130309 14:44:49 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:44:50 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168112! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:45:05 InnoDB: Assertion failure in thread 140320096368384 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:45:05 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=8 max_threads=151 thread_count=8 connection_count=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f9edf03a500] /lib64/libc.so.6(gsignal+0x35) [0x7f9edd6c98a5] /lib64/libc.so.6(abort+0x175) [0x7f9edd6cb085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f9edf032851] /lib64/libc.so.6(clone+0x6d) [0x7f9edd77f90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:45:05 mysqld_safe Number of processes running now: 0 130309 14:45:05 mysqld_safe mysqld restarted 130309 14:45:05 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:45:05 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892803710 130309 14:45:05 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892804684 130309 14:45:05 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:45:05 InnoDB: Started; log sequence number 0 892804684 130309 14:45:05 [Note] Event Scheduler: Loaded 0 events 130309 14:45:05 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:45:06 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168115! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:45:20 InnoDB: Assertion failure in thread 139832376375040 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:45:20 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f2d500dd500] /lib64/libc.so.6(gsignal+0x35) [0x7f2d4e76c8a5] /lib64/libc.so.6(abort+0x175) [0x7f2d4e76e085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f2d500d5851] /lib64/libc.so.6(clone+0x6d) [0x7f2d4e82290d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:45:20 mysqld_safe Number of processes running now: 0 130309 14:45:20 mysqld_safe mysqld restarted 130309 14:45:20 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:45:20 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892804684 130309 14:45:20 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892805644 130309 14:45:20 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:45:21 InnoDB: Started; log sequence number 0 892805644 130309 14:45:21 [Note] Event Scheduler: Loaded 0 events 130309 14:45:21 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:45:22 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168118! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:45:35 InnoDB: Assertion failure in thread 139947596044032 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:45:35 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f4828076500] /lib64/libc.so.6(gsignal+0x35) [0x7f48267058a5] /lib64/libc.so.6(abort+0x175) [0x7f4826707085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f482806e851] /lib64/libc.so.6(clone+0x6d) [0x7f48267bb90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:45:35 mysqld_safe Number of processes running now: 0 130309 14:45:35 mysqld_safe mysqld restarted 130309 14:45:35 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:45:35 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892805644 130309 14:45:35 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892806588 130309 14:45:35 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:45:36 InnoDB: Started; log sequence number 0 892806588 130309 14:45:36 [Note] Event Scheduler: Loaded 0 events 130309 14:45:36 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:45:37 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168121! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 2936698501 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:45:50 InnoDB: Assertion failure in thread 140231443441408 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:45:50 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=4 max_threads=151 thread_count=4 connection_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f8a3a687500] /lib64/libc.so.6(gsignal+0x35) [0x7f8a38d168a5] /lib64/libc.so.6(abort+0x175) [0x7f8a38d18085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f8a3a67f851] /lib64/libc.so.6(clone+0x6d) [0x7f8a38dcc90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:45:50 mysqld_safe Number of processes running now: 0 130309 14:45:50 mysqld_safe mysqld restarted 130309 14:45:50 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:45:50 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892806588 130309 14:45:50 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892807548 130309 14:45:50 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:45:51 InnoDB: Started; log sequence number 0 892807548 130309 14:45:51 [Note] Event Scheduler: Loaded 0 events 130309 14:45:51 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:45:52 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168124! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:46:05 InnoDB: Assertion failure in thread 140536270030592 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:46:05 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fd1337da500] /lib64/libc.so.6(gsignal+0x35) [0x7fd131e698a5] /lib64/libc.so.6(abort+0x175) [0x7fd131e6b085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fd1337d2851] /lib64/libc.so.6(clone+0x6d) [0x7fd131f1f90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:46:05 mysqld_safe Number of processes running now: 0 130309 14:46:05 mysqld_safe mysqld restarted 130309 14:46:05 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:46:05 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892807548 130309 14:46:05 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892809311 130309 14:46:05 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:46:06 InnoDB: Started; log sequence number 0 892809311 130309 14:46:06 [Note] Event Scheduler: Loaded 0 events 130309 14:46:06 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:46:07 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168127! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:46:21 InnoDB: Assertion failure in thread 139791746164480 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:46:21 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f23d9d0b500] /lib64/libc.so.6(gsignal+0x35) [0x7f23d839a8a5] /lib64/libc.so.6(abort+0x175) [0x7f23d839c085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f23d9d03851] /lib64/libc.so.6(clone+0x6d) [0x7f23d845090d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:46:21 mysqld_safe Number of processes running now: 0 130309 14:46:21 mysqld_safe mysqld restarted 130309 14:46:21 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:46:21 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892809311 130309 14:46:21 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892810313 130309 14:46:21 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:46:21 InnoDB: Started; log sequence number 0 892810313 130309 14:46:21 [Note] Event Scheduler: Loaded 0 events 130309 14:46:21 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:46:22 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168130! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:46:36 InnoDB: Assertion failure in thread 140029005346560 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:46:36 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f5b1809c500] /lib64/libc.so.6(gsignal+0x35) [0x7f5b1672b8a5] /lib64/libc.so.6(abort+0x175) [0x7f5b1672d085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f5b18094851] /lib64/libc.so.6(clone+0x6d) [0x7f5b167e190d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:46:36 mysqld_safe Number of processes running now: 0 130309 14:46:36 mysqld_safe mysqld restarted 130309 14:46:36 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:46:36 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892810313 130309 14:46:36 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892811257 130309 14:46:36 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:46:37 InnoDB: Started; log sequence number 0 892811257 130309 14:46:37 [Note] Event Scheduler: Loaded 0 events 130309 14:46:37 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:46:38 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168133! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:46:51 InnoDB: Assertion failure in thread 139713298020096 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:46:51 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f1196b48500] /lib64/libc.so.6(gsignal+0x35) [0x7f11951d78a5] /lib64/libc.so.6(abort+0x175) [0x7f11951d9085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f1196b40851] /lib64/libc.so.6(clone+0x6d) [0x7f119528d90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:46:51 mysqld_safe Number of processes running now: 0 130309 14:46:51 mysqld_safe mysqld restarted 130309 14:46:51 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:46:51 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892811257 130309 14:46:51 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892812217 130309 14:46:51 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:46:52 InnoDB: Started; log sequence number 0 892812217 130309 14:46:52 [Note] Event Scheduler: Loaded 0 events 130309 14:46:52 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:46:53 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168136! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:47:06 InnoDB: Assertion failure in thread 140237594425088 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:47:06 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f8baca4a500] /lib64/libc.so.6(gsignal+0x35) [0x7f8bab0d98a5] /lib64/libc.so.6(abort+0x175) [0x7f8bab0db085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f8baca42851] /lib64/libc.so.6(clone+0x6d) [0x7f8bab18f90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:47:06 mysqld_safe Number of processes running now: 0 130309 14:47:06 mysqld_safe mysqld restarted 130309 14:47:07 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:47:07 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892812217 130309 14:47:07 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892813177 130309 14:47:07 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:47:07 InnoDB: Started; log sequence number 0 892813177 130309 14:47:07 [Note] Event Scheduler: Loaded 0 events 130309 14:47:07 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:47:08 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168139! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:47:22 InnoDB: Assertion failure in thread 140078447838976 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:47:22 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f669ad33500] /lib64/libc.so.6(gsignal+0x35) [0x7f66993c28a5] /lib64/libc.so.6(abort+0x175) [0x7f66993c4085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f669ad2b851] /lib64/libc.so.6(clone+0x6d) [0x7f669947890d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:47:22 mysqld_safe Number of processes running now: 0 130309 14:47:22 mysqld_safe mysqld restarted 130309 14:47:22 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:47:22 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892813177 130309 14:47:22 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892814137 130309 14:47:22 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:47:22 InnoDB: Started; log sequence number 0 892814137 130309 14:47:22 [Note] Event Scheduler: Loaded 0 events 130309 14:47:22 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:47:23 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168142! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:47:37 InnoDB: Assertion failure in thread 139765338859264 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:47:37 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f1db839d500] /lib64/libc.so.6(gsignal+0x35) [0x7f1db6a2c8a5] /lib64/libc.so.6(abort+0x175) [0x7f1db6a2e085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f1db8395851] /lib64/libc.so.6(clone+0x6d) [0x7f1db6ae290d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:47:37 mysqld_safe Number of processes running now: 0 130309 14:47:37 mysqld_safe mysqld restarted 130309 14:47:37 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:47:37 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892814137 130309 14:47:37 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892815097 130309 14:47:37 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:47:37 InnoDB: Started; log sequence number 0 892815097 130309 14:47:37 [Note] Event Scheduler: Loaded 0 events 130309 14:47:37 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:47:38 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168145! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:47:52 InnoDB: Assertion failure in thread 139963207206656 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:47:52 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f4bc6572500] /lib64/libc.so.6(gsignal+0x35) [0x7f4bc4c018a5] /lib64/libc.so.6(abort+0x175) [0x7f4bc4c03085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f4bc656a851] /lib64/libc.so.6(clone+0x6d) [0x7f4bc4cb790d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:47:52 mysqld_safe Number of processes running now: 0 130309 14:47:52 mysqld_safe mysqld restarted 130309 14:47:52 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:47:52 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892815097 130309 14:47:52 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892816057 130309 14:47:52 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:47:52 InnoDB: Started; log sequence number 0 892816057 130309 14:47:53 [Note] Event Scheduler: Loaded 0 events 130309 14:47:53 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:47:54 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168148! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:48:07 InnoDB: Assertion failure in thread 140514542167808 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:48:07 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fcc2472b500] /lib64/libc.so.6(gsignal+0x35) [0x7fcc22dba8a5] /lib64/libc.so.6(abort+0x175) [0x7fcc22dbc085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fcc24723851] /lib64/libc.so.6(clone+0x6d) [0x7fcc22e7090d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:48:07 mysqld_safe Number of processes running now: 0 130309 14:48:07 mysqld_safe mysqld restarted 130309 14:48:07 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:48:07 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892816057 130309 14:48:07 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892817017 130309 14:48:07 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:48:08 InnoDB: Started; log sequence number 0 892817017 130309 14:48:08 [Note] Event Scheduler: Loaded 0 events 130309 14:48:08 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:48:09 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168151! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:48:22 InnoDB: Assertion failure in thread 140433376130816 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:48:22 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fb93f037500] /lib64/libc.so.6(gsignal+0x35) [0x7fb93d6c68a5] /lib64/libc.so.6(abort+0x175) [0x7fb93d6c8085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fb93f02f851] /lib64/libc.so.6(clone+0x6d) [0x7fb93d77c90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:48:22 mysqld_safe Number of processes running now: 0 130309 14:48:22 mysqld_safe mysqld restarted 130309 14:48:23 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:48:23 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892817017 130309 14:48:23 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892817977 130309 14:48:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:48:23 InnoDB: Started; log sequence number 0 892817977 130309 14:48:23 [Note] Event Scheduler: Loaded 0 events 130309 14:48:23 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:48:24 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168154! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:48:37 InnoDB: Assertion failure in thread 140659119859456 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:48:37 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fedce255500] /lib64/libc.so.6(gsignal+0x35) [0x7fedcc8e48a5] /lib64/libc.so.6(abort+0x175) [0x7fedcc8e6085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fedce24d851] /lib64/libc.so.6(clone+0x6d) [0x7fedcc99a90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:48:37 mysqld_safe Number of processes running now: 0 130309 14:48:37 mysqld_safe mysqld restarted 130309 14:48:38 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:48:38 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892817977 130309 14:48:38 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892818922 130309 14:48:38 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:48:38 InnoDB: Started; log sequence number 0 892818922 130309 14:48:38 [Note] Event Scheduler: Loaded 0 events 130309 14:48:38 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:48:39 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168157! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:48:53 InnoDB: Assertion failure in thread 140154100459264 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:48:53 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f783872b500] /lib64/libc.so.6(gsignal+0x35) [0x7f7836dba8a5] /lib64/libc.so.6(abort+0x175) [0x7f7836dbc085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f7838723851] /lib64/libc.so.6(clone+0x6d) [0x7f7836e7090d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:48:53 mysqld_safe Number of processes running now: 0 130309 14:48:53 mysqld_safe mysqld restarted 130309 14:48:53 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:48:53 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892818922 130309 14:48:53 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892819882 130309 14:48:53 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:48:53 InnoDB: Started; log sequence number 0 892819882 130309 14:48:53 [Note] Event Scheduler: Loaded 0 events 130309 14:48:53 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:48:54 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168160! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:49:08 InnoDB: Assertion failure in thread 140327029561088 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:49:08 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fa07fd32500] /lib64/libc.so.6(gsignal+0x35) [0x7fa07e3c18a5] /lib64/libc.so.6(abort+0x175) [0x7fa07e3c3085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fa07fd2a851] /lib64/libc.so.6(clone+0x6d) [0x7fa07e47790d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:49:08 mysqld_safe Number of processes running now: 0 130309 14:49:08 mysqld_safe mysqld restarted 130309 14:49:08 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:49:08 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892819882 130309 14:49:08 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892820842 130309 14:49:08 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:49:08 InnoDB: Started; log sequence number 0 892820842 130309 14:49:08 [Note] Event Scheduler: Loaded 0 events 130309 14:49:08 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:49:09 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168163! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:49:23 InnoDB: Assertion failure in thread 140626469312256 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:49:23 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fe6381e4500] /lib64/libc.so.6(gsignal+0x35) [0x7fe6368738a5] /lib64/libc.so.6(abort+0x175) [0x7fe636875085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fe6381dc851] /lib64/libc.so.6(clone+0x6d) [0x7fe63692990d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:49:23 mysqld_safe Number of processes running now: 0 130309 14:49:23 mysqld_safe mysqld restarted 130309 14:49:23 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:49:23 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892820842 130309 14:49:23 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892821802 130309 14:49:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:49:24 InnoDB: Started; log sequence number 0 892821802 130309 14:49:24 [Note] Event Scheduler: Loaded 0 events 130309 14:49:24 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:49:25 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168166! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:49:38 InnoDB: Assertion failure in thread 140220898977536 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:49:38 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f87c6062500] /lib64/libc.so.6(gsignal+0x35) [0x7f87c46f18a5] /lib64/libc.so.6(abort+0x175) [0x7f87c46f3085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f87c605a851] /lib64/libc.so.6(clone+0x6d) [0x7f87c47a790d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:49:38 mysqld_safe Number of processes running now: 0 130309 14:49:38 mysqld_safe mysqld restarted 130309 14:49:38 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:49:38 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892821802 130309 14:49:38 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892822762 130309 14:49:38 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:49:39 InnoDB: Started; log sequence number 0 892822762 130309 14:49:39 [Note] Event Scheduler: Loaded 0 events 130309 14:49:39 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:49:40 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168169! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:49:53 InnoDB: Assertion failure in thread 140180537161472 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:49:53 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f7e602f5500] /lib64/libc.so.6(gsignal+0x35) [0x7f7e5e9848a5] /lib64/libc.so.6(abort+0x175) [0x7f7e5e986085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f7e602ed851] /lib64/libc.so.6(clone+0x6d) [0x7f7e5ea3a90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:49:53 mysqld_safe Number of processes running now: 0 130309 14:49:53 mysqld_safe mysqld restarted 130309 14:49:53 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:49:53 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892822762 130309 14:49:53 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892823722 130309 14:49:53 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:49:54 InnoDB: Started; log sequence number 0 892823722 130309 14:49:54 [Note] Event Scheduler: Loaded 0 events 130309 14:49:54 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:49:55 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168172! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 706920905 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:50:08 InnoDB: Assertion failure in thread 139782988490496 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:50:08 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=7 max_threads=151 thread_count=7 connection_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f21d4db5500] /lib64/libc.so.6(gsignal+0x35) [0x7f21d34448a5] /lib64/libc.so.6(abort+0x175) [0x7f21d3446085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f21d4dad851] /lib64/libc.so.6(clone+0x6d) [0x7f21d34fa90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:50:08 mysqld_safe Number of processes running now: 0 130309 14:50:08 mysqld_safe mysqld restarted 130309 14:50:09 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:50:09 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892823722 130309 14:50:09 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892825510 130309 14:50:09 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:50:09 InnoDB: Started; log sequence number 0 892825510 130309 14:50:09 [Note] Event Scheduler: Loaded 0 events 130309 14:50:09 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:50:10 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168175! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:50:24 InnoDB: Assertion failure in thread 140632865634048 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:50:24 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fe7b58c5500] /lib64/libc.so.6(gsignal+0x35) [0x7fe7b3f548a5] /lib64/libc.so.6(abort+0x175) [0x7fe7b3f56085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fe7b58bd851] /lib64/libc.so.6(clone+0x6d) [0x7fe7b400a90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:50:24 mysqld_safe Number of processes running now: 0 130309 14:50:24 mysqld_safe mysqld restarted 130309 14:50:24 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:50:24 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892825510 130309 14:50:24 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892826469 130309 14:50:24 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:50:24 InnoDB: Started; log sequence number 0 892826469 130309 14:50:24 [Note] Event Scheduler: Loaded 0 events 130309 14:50:24 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:50:25 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168178! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com 130309 14:50:30 [Note] /usr/libexec/mysqld: Normal shutdown 130309 14:50:30 [Note] Event Scheduler: Purging the queue. 0 events 130309 14:50:32 InnoDB: Starting shutdown... 130309 14:50:35 InnoDB: Shutdown completed; log sequence number 0 892826787 130309 14:50:35 [Note] /usr/libexec/mysqld: Shutdown complete 130309 14:50:35 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 14:50:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 14:50:36 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:50:36 InnoDB: Completed initialization of buffer pool 130309 14:50:36 InnoDB: Started; log sequence number 0 892826787 130309 14:50:36 [Note] Event Scheduler: Loaded 0 events 130309 14:50:36 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:50:46 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168181! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:50:58 InnoDB: Assertion failure in thread 140323774748416 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:50:58 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=7 max_threads=151 thread_count=7 connection_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f9fb9d89500] /lib64/libc.so.6(gsignal+0x35) [0x7f9fb84188a5] /lib64/libc.so.6(abort+0x175) [0x7f9fb841a085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f9fb9d81851] /lib64/libc.so.6(clone+0x6d) [0x7f9fb84ce90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:50:58 mysqld_safe Number of processes running now: 0 130309 14:50:58 mysqld_safe mysqld restarted 130309 14:50:58 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:50:58 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892827397 130309 14:50:58 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892828389 130309 14:50:58 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:50:59 InnoDB: Started; log sequence number 0 892828389 130309 14:50:59 [Note] Event Scheduler: Loaded 0 events 130309 14:50:59 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:51:00 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168184! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:51:14 InnoDB: Assertion failure in thread 140163025987328 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:51:14 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f7a510a9500] /lib64/libc.so.6(gsignal+0x35) [0x7f7a4f7388a5] /lib64/libc.so.6(abort+0x175) [0x7f7a4f73a085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f7a510a1851] /lib64/libc.so.6(clone+0x6d) [0x7f7a4f7ee90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:51:14 mysqld_safe Number of processes running now: 0 130309 14:51:14 mysqld_safe mysqld restarted 130309 14:51:14 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:51:14 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892828389 130309 14:51:14 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892829350 130309 14:51:14 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:51:15 InnoDB: Started; log sequence number 0 892829350 130309 14:51:15 [Note] Event Scheduler: Loaded 0 events 130309 14:51:15 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:51:16 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168187! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:51:29 InnoDB: Assertion failure in thread 140291549951744 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:51:29 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f983dbb0500] /lib64/libc.so.6(gsignal+0x35) [0x7f983c23f8a5] /lib64/libc.so.6(abort+0x175) [0x7f983c241085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f983dba8851] /lib64/libc.so.6(clone+0x6d) [0x7f983c2f590d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:51:29 mysqld_safe Number of processes running now: 0 130309 14:51:29 mysqld_safe mysqld restarted 130309 14:51:29 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:51:29 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892829350 130309 14:51:29 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892830310 130309 14:51:29 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:51:30 InnoDB: Started; log sequence number 0 892830310 130309 14:51:30 [Note] Event Scheduler: Loaded 0 events 130309 14:51:30 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:51:31 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168190! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:51:44 InnoDB: Assertion failure in thread 140142970926848 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:51:44 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=5 max_threads=151 thread_count=5 connection_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f75a53f1500] /lib64/libc.so.6(gsignal+0x35) [0x7f75a3a808a5] /lib64/libc.so.6(abort+0x175) [0x7f75a3a82085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f75a53e9851] /lib64/libc.so.6(clone+0x6d) [0x7f75a3b3690d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:51:44 mysqld_safe Number of processes running now: 0 130309 14:51:44 mysqld_safe mysqld restarted 130309 14:51:44 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:51:44 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892830310 130309 14:51:44 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892831270 130309 14:51:44 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:51:45 InnoDB: Started; log sequence number 0 892831270 130309 14:51:45 [Note] Event Scheduler: Loaded 0 events 130309 14:51:45 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:51:46 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168193! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:52:00 InnoDB: Assertion failure in thread 140651144394496 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:52:00 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7febf2902500] /lib64/libc.so.6(gsignal+0x35) [0x7febf0f918a5] /lib64/libc.so.6(abort+0x175) [0x7febf0f93085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7febf28fa851] /lib64/libc.so.6(clone+0x6d) [0x7febf104790d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:52:00 mysqld_safe Number of processes running now: 0 130309 14:52:00 mysqld_safe mysqld restarted 130309 14:52:00 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:52:00 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892831270 130309 14:52:00 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892832214 130309 14:52:00 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:52:00 InnoDB: Started; log sequence number 0 892832214 130309 14:52:00 [Note] Event Scheduler: Loaded 0 events 130309 14:52:00 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:52:01 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168196! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:52:15 InnoDB: Assertion failure in thread 139959195502336 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:52:15 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f4ad72a2500] /lib64/libc.so.6(gsignal+0x35) [0x7f4ad59318a5] /lib64/libc.so.6(abort+0x175) [0x7f4ad5933085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f4ad729a851] /lib64/libc.so.6(clone+0x6d) [0x7f4ad59e790d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:52:15 mysqld_safe Number of processes running now: 0 130309 14:52:15 mysqld_safe mysqld restarted 130309 14:52:15 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:52:15 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892832214 130309 14:52:15 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892833174 130309 14:52:15 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:52:15 InnoDB: Started; log sequence number 0 892833174 130309 14:52:15 [Note] Event Scheduler: Loaded 0 events 130309 14:52:15 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:52:16 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168199! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:52:30 InnoDB: Assertion failure in thread 139902400308992 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:52:30 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f3d9d7fb500] /lib64/libc.so.6(gsignal+0x35) [0x7f3d9be8a8a5] /lib64/libc.so.6(abort+0x175) [0x7f3d9be8c085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f3d9d7f3851] /lib64/libc.so.6(clone+0x6d) [0x7f3d9bf4090d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:52:30 mysqld_safe Number of processes running now: 0 130309 14:52:30 mysqld_safe mysqld restarted 130309 14:52:30 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:52:30 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892833174 130309 14:52:30 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892834134 130309 14:52:30 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:52:31 InnoDB: Started; log sequence number 0 892834134 130309 14:52:31 [Note] Event Scheduler: Loaded 0 events 130309 14:52:31 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:52:32 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168202! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:52:45 InnoDB: Assertion failure in thread 140408722028288 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:52:45 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=5 max_threads=151 thread_count=5 connection_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fb3853f6500] /lib64/libc.so.6(gsignal+0x35) [0x7fb383a858a5] /lib64/libc.so.6(abort+0x175) [0x7fb383a87085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fb3853ee851] /lib64/libc.so.6(clone+0x6d) [0x7fb383b3b90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:52:45 mysqld_safe Number of processes running now: 0 130309 14:52:45 mysqld_safe mysqld restarted 130309 14:52:45 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:52:45 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892834134 130309 14:52:45 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892835094 130309 14:52:45 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:52:46 InnoDB: Started; log sequence number 0 892835094 130309 14:52:46 [Note] Event Scheduler: Loaded 0 events 130309 14:52:46 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:52:47 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168205! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:53:00 InnoDB: Assertion failure in thread 140026189649664 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:53:00 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f5a6fb60500] /lib64/libc.so.6(gsignal+0x35) [0x7f5a6e1ef8a5] /lib64/libc.so.6(abort+0x175) [0x7f5a6e1f1085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f5a6fb58851] /lib64/libc.so.6(clone+0x6d) [0x7f5a6e2a590d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:53:00 mysqld_safe Number of processes running now: 0 130309 14:53:00 mysqld_safe mysqld restarted 130309 14:53:00 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:53:00 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892835094 130309 14:53:00 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892836054 130309 14:53:00 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:53:01 InnoDB: Started; log sequence number 0 892836054 130309 14:53:01 [Note] Event Scheduler: Loaded 0 events 130309 14:53:01 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:53:02 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168208! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:53:15 InnoDB: Assertion failure in thread 139673523443456 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:53:15 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f08586bd500] /lib64/libc.so.6(gsignal+0x35) [0x7f0856d4c8a5] /lib64/libc.so.6(abort+0x175) [0x7f0856d4e085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f08586b5851] /lib64/libc.so.6(clone+0x6d) [0x7f0856e0290d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:53:15 mysqld_safe Number of processes running now: 0 130309 14:53:15 mysqld_safe mysqld restarted 130309 14:53:15 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:53:15 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892836054 130309 14:53:15 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892837014 130309 14:53:16 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:53:16 InnoDB: Started; log sequence number 0 892837014 130309 14:53:16 [Note] Event Scheduler: Loaded 0 events 130309 14:53:16 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:53:17 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168211! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:53:31 InnoDB: Assertion failure in thread 140074870089472 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:53:31 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f65c5684500] /lib64/libc.so.6(gsignal+0x35) [0x7f65c3d138a5] /lib64/libc.so.6(abort+0x175) [0x7f65c3d15085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f65c567c851] /lib64/libc.so.6(clone+0x6d) [0x7f65c3dc990d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:53:31 mysqld_safe Number of processes running now: 0 130309 14:53:31 mysqld_safe mysqld restarted 130309 14:53:31 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:53:31 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892837014 130309 14:53:31 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892847250 130309 14:53:31 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:53:31 InnoDB: Started; log sequence number 0 892847250 130309 14:53:31 [Note] Event Scheduler: Loaded 0 events 130309 14:53:31 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:53:32 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168214! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:53:46 InnoDB: Assertion failure in thread 139983289739008 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:53:46 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=5 max_threads=151 thread_count=5 connection_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f50734cd500] /lib64/libc.so.6(gsignal+0x35) [0x7f5071b5c8a5] /lib64/libc.so.6(abort+0x175) [0x7f5071b5e085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f50734c5851] /lib64/libc.so.6(clone+0x6d) [0x7f5071c1290d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:53:46 mysqld_safe Number of processes running now: 0 130309 14:53:46 mysqld_safe mysqld restarted 130309 14:53:46 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:53:46 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892847250 130309 14:53:46 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892848211 130309 14:53:46 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:53:46 InnoDB: Started; log sequence number 0 892848211 130309 14:53:46 [Note] Event Scheduler: Loaded 0 events 130309 14:53:46 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:53:47 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168217! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:54:01 InnoDB: Assertion failure in thread 140642218915584 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:54:01 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fe9decc5500] /lib64/libc.so.6(gsignal+0x35) [0x7fe9dd3548a5] /lib64/libc.so.6(abort+0x175) [0x7fe9dd356085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fe9decbd851] /lib64/libc.so.6(clone+0x6d) [0x7fe9dd40a90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:54:01 mysqld_safe Number of processes running now: 0 130309 14:54:01 mysqld_safe mysqld restarted 130309 14:54:01 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:54:01 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892848211 130309 14:54:01 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892849171 130309 14:54:01 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:54:01 InnoDB: Started; log sequence number 0 892849171 130309 14:54:01 [Note] Event Scheduler: Loaded 0 events 130309 14:54:01 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:54:02 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168220! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3734038583 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:54:16 InnoDB: Assertion failure in thread 140176091236096 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:54:16 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f7d56a80500] /lib64/libc.so.6(gsignal+0x35) [0x7f7d5510f8a5] /lib64/libc.so.6(abort+0x175) [0x7f7d55111085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f7d56a78851] /lib64/libc.so.6(clone+0x6d) [0x7f7d551c590d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:54:16 mysqld_safe Number of processes running now: 0 130309 14:54:16 mysqld_safe mysqld restarted 130309 14:54:16 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:54:16 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892849171 130309 14:54:16 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892850132 130309 14:54:16 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:54:17 InnoDB: Started; log sequence number 0 892850132 130309 14:54:17 [Note] Event Scheduler: Loaded 0 events 130309 14:54:17 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:54:18 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168223! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1498188075 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:54:31 InnoDB: Assertion failure in thread 140064879240960 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:54:31 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7f6371e31500] /lib64/libc.so.6(gsignal+0x35) [0x7f63704c08a5] /lib64/libc.so.6(abort+0x175) [0x7f63704c2085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7f6371e29851] /lib64/libc.so.6(clone+0x6d) [0x7f637057690d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:54:31 mysqld_safe Number of processes running now: 0 130309 14:54:31 mysqld_safe mysqld restarted 130309 14:54:31 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:54:31 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892850132 130309 14:54:31 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892851918 130309 14:54:31 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:54:32 InnoDB: Started; log sequence number 0 892851918 130309 14:54:32 [Note] Event Scheduler: Loaded 0 events 130309 14:54:32 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:54:33 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168226! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1498188075 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:54:46 InnoDB: Assertion failure in thread 140523658532608 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:54:46 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=5 max_threads=151 thread_count=5 connection_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fce47d2e500] /lib64/libc.so.6(gsignal+0x35) [0x7fce463bd8a5] /lib64/libc.so.6(abort+0x175) [0x7fce463bf085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fce47d26851] /lib64/libc.so.6(clone+0x6d) [0x7fce4647390d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:54:46 mysqld_safe Number of processes running now: 0 130309 14:54:46 mysqld_safe mysqld restarted 130309 14:54:46 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:54:46 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892851918 130309 14:54:46 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892852878 130309 14:54:46 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:54:47 InnoDB: Started; log sequence number 0 892852878 130309 14:54:47 [Note] Event Scheduler: Loaded 0 events 130309 14:54:47 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:54:48 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168229! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1498188075 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:55:01 InnoDB: Assertion failure in thread 140601313928960 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:55:01 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=6 max_threads=151 thread_count=6 connection_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fe058771500] /lib64/libc.so.6(gsignal+0x35) [0x7fe056e008a5] /lib64/libc.so.6(abort+0x175) [0x7fe056e02085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fe058769851] /lib64/libc.so.6(clone+0x6d) [0x7fe056eb690d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:55:01 mysqld_safe Number of processes running now: 0 130309 14:55:02 mysqld_safe mysqld restarted 130309 14:55:02 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:55:02 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892852878 130309 14:55:02 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892853838 130309 14:55:02 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:55:02 InnoDB: Started; log sequence number 0 892853838 130309 14:55:02 [Note] Event Scheduler: Loaded 0 events 130309 14:55:02 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:55:03 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168232! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 1498188075 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 14:55:17 InnoDB: Assertion failure in thread 139636680677120 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:55:17 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=2 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7effc4595500] /lib64/libc.so.6(gsignal+0x35) [0x7effc2c248a5] /lib64/libc.so.6(abort+0x175) [0x7effc2c26085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7effc458d851] /lib64/libc.so.6(clone+0x6d) [0x7effc2cda90d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 14:55:17 mysqld_safe Number of processes running now: 0 130309 14:55:17 mysqld_safe mysqld restarted 130309 14:55:17 InnoDB: Initializing buffer pool, size = 8.0M 130309 14:55:17 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892853838 130309 14:55:17 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 892854182 130309 14:55:17 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 14:55:17 InnoDB: Started; log sequence number 0 892854182 130309 14:55:17 [Note] Event Scheduler: Loaded 0 events 130309 14:55:17 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 14:55:18 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168233! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com 130309 15:02:16 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:02:16 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:02:16 InnoDB: Starting shutdown... 130309 15:02:19 InnoDB: Shutdown completed; log sequence number 0 892854192 130309 15:02:19 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:02:19 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:02:20 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:02:20 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:02:20 InnoDB: Completed initialization of buffer pool 130309 15:02:20 InnoDB: Started; log sequence number 0 892854192 InnoDB: !!! innodb_force_recovery is set to 4 !!! 130309 15:02:20 [Note] Event Scheduler: Loaded 0 events 130309 15:02:20 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:02:50 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:02:50 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:02:50 InnoDB: Starting shutdown... 130309 15:02:55 InnoDB: Shutdown completed; log sequence number 0 892854192 130309 15:02:55 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:02:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:02:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:02:57 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:02:57 InnoDB: Completed initialization of buffer pool 130309 15:02:57 InnoDB: Started; log sequence number 0 892854192 130309 15:02:57 [Note] Event Scheduler: Loaded 0 events 130309 15:02:57 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:02:58 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168233! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com InnoDB: Error: trying to access page number 3550163875 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 130309 15:07:42 InnoDB: Assertion failure in thread 140573866452736 in file fil/fil0fil.c line 4135 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 22:07:42 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338332 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x84e269] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a2d73] /lib64/libpthread.so.0(+0xf500) [0x7fd9f8df3500] /lib64/libc.so.6(gsignal+0x35) [0x7fd9f74828a5] /lib64/libc.so.6(abort+0x175) [0x7fd9f7484085] /usr/libexec/mysqld(fil_io+0x36e) [0x76607e] /usr/libexec/mysqld() [0x74df33] /usr/libexec/mysqld(buf_read_page+0x225) [0x74e975] /usr/libexec/mysqld(buf_page_get_gen+0x393) [0x747e53] /usr/libexec/mysqld() [0x7cadb9] /usr/libexec/mysqld() [0x7cb425] /usr/libexec/mysqld(trx_purge_fetch_next_rec+0x218) [0x7cc488] /usr/libexec/mysqld(row_purge_step+0x40) [0x7b1080] /usr/libexec/mysqld(que_run_threads+0x55b) [0x7a04bb] /usr/libexec/mysqld(trx_purge+0x332) [0x7ca6c2] /usr/libexec/mysqld(srv_master_thread+0x58d) [0x7c2efd] /lib64/libpthread.so.0(+0x7851) [0x7fd9f8deb851] /lib64/libc.so.6(clone+0x6d) [0x7fd9f753890d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130309 15:07:42 mysqld_safe Number of processes running now: 0 130309 15:07:42 mysqld_safe mysqld restarted 130309 15:07:42 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:07:42 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 0 892854192 130309 15:07:42 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 893011937 130309 15:07:42 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed 130309 15:07:43 InnoDB: Started; log sequence number 0 893011937 130309 15:07:43 [Note] Event Scheduler: Loaded 0 events 130309 15:07:43 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:07:44 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168259! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com 130309 15:08:05 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:08:05 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:08:05 InnoDB: Starting shutdown... 130309 15:08:08 InnoDB: Shutdown completed; log sequence number 0 893011937 130309 15:08:08 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:08:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:08:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:08:09 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:08:09 InnoDB: Completed initialization of buffer pool 130309 15:08:09 InnoDB: Started; log sequence number 0 893011937 130309 15:08:09 [Note] Event Scheduler: Loaded 0 events 130309 15:08:09 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:08:10 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168259! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com 130309 15:09:09 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:09:09 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:09:09 InnoDB: Starting shutdown... 130309 15:09:09 InnoDB: Shutdown completed; log sequence number 0 893011937 130309 15:09:09 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:09:10 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:09:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:09:10 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:09:10 InnoDB: Completed initialization of buffer pool 130309 15:09:10 InnoDB: Started; log sequence number 0 893011937 InnoDB: !!! innodb_force_recovery is set to 1 !!! 130309 15:09:10 [Note] Event Scheduler: Loaded 0 events 130309 15:09:10 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:09:11 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168259! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com 130309 15:09:34 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:09:34 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:09:34 InnoDB: Starting shutdown... 130309 15:09:36 InnoDB: Shutdown completed; log sequence number 0 893011937 130309 15:09:36 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:09:36 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:09:37 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:09:37 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:09:37 InnoDB: Completed initialization of buffer pool 130309 15:09:37 InnoDB: Started; log sequence number 0 893011937 InnoDB: !!! innodb_force_recovery is set to 2 !!! 130309 15:09:37 [Note] Event Scheduler: Loaded 0 events 130309 15:09:37 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:09:50 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:09:50 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:09:50 InnoDB: Starting shutdown... 130309 15:09:52 InnoDB: Shutdown completed; log sequence number 0 893011937 130309 15:09:52 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:09:52 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:09:53 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:09:53 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:09:53 InnoDB: Completed initialization of buffer pool 130309 15:09:53 InnoDB: Started; log sequence number 0 893011937 InnoDB: !!! innodb_force_recovery is set to 3 !!! 130309 15:09:53 [Note] Event Scheduler: Loaded 0 events 130309 15:09:53 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:10:00 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:10:00 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:10:00 InnoDB: Starting shutdown... 130309 15:10:03 InnoDB: Shutdown completed; log sequence number 0 893011937 130309 15:10:03 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:10:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:10:04 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:10:05 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:10:05 InnoDB: Completed initialization of buffer pool 130309 15:10:05 InnoDB: Started; log sequence number 0 893011937 InnoDB: !!! innodb_force_recovery is set to 4 !!! 130309 15:10:05 [Note] Event Scheduler: Loaded 0 events 130309 15:10:05 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:10:11 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:10:11 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:10:11 InnoDB: Starting shutdown... 130309 15:10:15 InnoDB: Shutdown completed; log sequence number 0 893011937 130309 15:10:15 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:10:15 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:10:16 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:10:16 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:10:16 InnoDB: Completed initialization of buffer pool 130309 15:10:16 InnoDB: Started; log sequence number 0 893011937 InnoDB: !!! innodb_force_recovery is set to 5 !!! 130309 15:10:16 [Note] Event Scheduler: Loaded 0 events 130309 15:10:16 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:10:22 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:10:22 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:10:22 InnoDB: Starting shutdown... 130309 15:10:26 InnoDB: Shutdown completed; log sequence number 0 893011937 130309 15:10:26 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:10:26 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:10:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:10:28 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:10:28 InnoDB: Completed initialization of buffer pool InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on InnoDB: Skipping log redo 130309 15:10:28 InnoDB: Started; log sequence number 0 0 InnoDB: !!! innodb_force_recovery is set to 6 !!! 130309 15:10:28 [Note] Event Scheduler: Loaded 0 events 130309 15:10:28 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:10:35 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:10:35 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:10:35 InnoDB: Starting shutdown... 130309 15:10:38 InnoDB: Shutdown completed; log sequence number 0 8204 130309 15:10:38 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:10:38 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:10:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:10:39 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:10:39 InnoDB: Completed initialization of buffer pool 130309 15:10:39 InnoDB: Error: page 7 log sequence number 0 128771 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 1 log sequence number 0 892773279 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 3 log sequence number 0 10675 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 2 log sequence number 0 893009573 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 4 log sequence number 0 889474116 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 11 log sequence number 0 893011437 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 5 log sequence number 0 892854202 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 6 log sequence number 0 893011937 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 51 log sequence number 0 893011937 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 32772 log sequence number 0 889509252 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 32769 log sequence number 0 892770898 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 32770 log sequence number 0 893011937 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 8 log sequence number 0 893011848 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 0 log sequence number 0 893011355 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 9 log sequence number 0 893011854 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 10 log sequence number 0 893011749 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 12 log sequence number 0 893011275 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 13 log sequence number 0 37356 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 14 log sequence number 0 37356 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 15 log sequence number 0 37356 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 47 log sequence number 0 41129 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Error: page 48 log sequence number 0 42350 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: for more information. 130309 15:10:39 InnoDB: Started; log sequence number 0 8204 130309 15:10:39 [Note] Event Scheduler: Loaded 0 events 130309 15:10:39 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:10:40 InnoDB: Warning: purge reached the head of the history list, InnoDB: but its length is still reported as 168259! Make a detailed bug InnoDB: report, and submit it to http://bugs.mysql.com 130309 15:12:02 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:12:02 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:12:02 InnoDB: Starting shutdown... 130309 15:12:05 InnoDB: Shutdown completed; log sequence number 0 8214 130309 15:12:05 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:12:05 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:12:56 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:12:56 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:12:56 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 130309 15:12:56 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 130309 15:12:56 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 130309 15:12:56 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 130309 15:12:56 InnoDB: Started; log sequence number 0 0 130309 15:12:56 [Note] Event Scheduler: Loaded 0 events 130309 15:12:56 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 130309 15:21:55 [Note] /usr/libexec/mysqld: Normal shutdown 130309 15:21:55 [Note] Event Scheduler: Purging the queue. 0 events 130309 15:21:55 InnoDB: Starting shutdown... 130309 15:21:57 InnoDB: Shutdown completed; log sequence number 0 557310041 130309 15:21:57 [Note] /usr/libexec/mysqld: Shutdown complete 130309 15:21:57 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 130309 15:21:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130309 15:21:59 InnoDB: Initializing buffer pool, size = 8.0M 130309 15:21:59 InnoDB: Completed initialization of buffer pool 130309 15:21:59 InnoDB: Started; log sequence number 0 557310041 130309 15:21:59 [Note] Event Scheduler: Loaded 0 events 130309 15:21:59 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.67' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution