090324 04:04:17 mysqld_safe Starting mysqld daemon with databases from /db/staging 090324 4:04:18 [Warning] Changed limits: max_open_files: 1024 max_connections: 300 table_cache: 357 090324 4:04:21 InnoDB: Started; log sequence number 0 46410 090324 4:04:21 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.30' socket: '/var/mysql/mysql.staging.sock' port: 4000 MySQL Community Server (GPL) Status information: Current dir: /db/staging/ Running threads: 1 Stack size: 262144 Current locks: lock: 0x9ed0190: write write : 0x9eca4a0 (1:13); ### ^^^ - this is the beginning of normal error log output from receiving HUP ### \/\/ - This is segfault dump 090324 4:06:06 - mysqld got signal 11 ; 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=33554432 read_buffer_size=4194304 max_used_connections=1 max_threads=300 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2493417 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 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 = (nil) thread_stack 0x40000 /opt/mysql/bin/mysqld(my_print_stacktrace+0x20) [0x9fa460] /opt/mysql/bin/mysqld(handle_segfault+0x368) [0x5fa992] /lib64/libpthread.so.0 [0x338180de70] /lib64/libc.so.6(strlen+0x10) [0x3381076150] /lib64/libc.so.6(_IO_vfprintf+0x3e9b) [0x338104605b] /lib64/libc.so.6(_IO_printf+0x9a) [0x338104be6a] /opt/mysql/bin/mysqld(mysql_print_status()+0x541) [0x6b129d] /opt/mysql/bin/mysqld(signal_hand+0x29f) [0x5f8d57] /lib64/libpthread.so.0 [0x33818062f7] /lib64/libc.so.6(clone+0x6d) [0x33810ce85d] 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. Key caches: default Buffer_size: 33554432 Block_size: 1024 Division_limit: 100 Age_limit: 300 blocks used: 228 not flushed: 0 w_requests: 12569 writes: 284 r_requests: 24767 reads: 0 handler status: read_key: 0 read_next: 0 read_rnd 0 read_first: 1 write: 635198 delete 0 update: 0 Table status: Opened tables: 110 Open tables: 1 Open files: 0 Open streams: 0 Alarm status: Active alarms: 0 Max used alarms: 1 Next alarm time: 0 Thread database.table_name Locked/Waiting Lock_type 1 prod_app.am_address Locked - write 090324 04:06:06 mysqld_safe Number of processes running now: 0 090324 04:06:06 mysqld_safe mysqld restarted 090324 4:06:06 [Warning] Changed limits: max_open_files: 1024 max_connections: 300 table_cache: 357 InnoDB: Log scan progressed past the checkpoint lsn 0 50908261 090324 4:06: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 56151040 InnoDB: Doing recovery: scanned up to log sequence number 0 61393920 InnoDB: Doing recovery: scanned up to log sequence number 0 66636800 InnoDB: Doing recovery: scanned up to log sequence number 0 71879680 InnoDB: Doing recovery: scanned up to log sequence number 0 77122560 InnoDB: Doing recovery: scanned up to log sequence number 0 82365440 InnoDB: Doing recovery: scanned up to log sequence number 0 87608320 InnoDB: Doing recovery: scanned up to log sequence number 0 92851200 InnoDB: Doing recovery: scanned up to log sequence number 0 98094080 InnoDB: Doing recovery: scanned up to log sequence number 0 103336960 InnoDB: Doing recovery: scanned up to log sequence number 0 108579840 InnoDB: Doing recovery: scanned up to log sequence number 0 113822720 InnoDB: Doing recovery: scanned up to log sequence number 0 119065600 InnoDB: Doing recovery: scanned up to log sequence number 0 124308480 InnoDB: Doing recovery: scanned up to log sequence number 0 129551360 InnoDB: Doing recovery: scanned up to log sequence number 0 134794240 InnoDB: Doing recovery: scanned up to log sequence number 0 140037120 InnoDB: Doing recovery: scanned up to log sequence number 0 145280000 090324 4:06:17 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 150522880 InnoDB: Doing recovery: scanned up to log sequence number 0 155765760 InnoDB: Doing recovery: scanned up to log sequence number 0 161008640 InnoDB: Doing recovery: scanned up to log sequence number 0 166251520 InnoDB: Doing recovery: scanned up to log sequence number 0 171494400 InnoDB: Doing recovery: scanned up to log sequence number 0 176737280 InnoDB: Doing recovery: scanned up to log sequence number 0 181980160 InnoDB: Doing recovery: scanned up to log sequence number 0 187223040 InnoDB: Doing recovery: scanned up to log sequence number 0 192465920 InnoDB: Doing recovery: scanned up to log sequence number 0 195371031 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 2266 row operations to undo InnoDB: Trx id counter is 0 1792 090324 4:06:40 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Starting in background the rollback of uncommitted transactions 090324 4:06:58 InnoDB: Rolling back trx with id 0 1523, 2266 rows to undo InnoDB: Progress in percents: 1090324 4:06:58 InnoDB: Started; log sequence number 0 195371031 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 35090324 4:06:58 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.30' socket: '/var/mysql/mysql.staging.sock' port: 4000 MySQL Community Server (GPL) 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 100 InnoDB: Rolling back of trx id 0 1523 completed 090324 4:06:58 InnoDB: Rollback of non-prepared transactions completed