root@debian /home# mysqld
130702 3:14:54 [Note] Plugin 'FEDERATED' is disabled.
130702 3:14:54 InnoDB: Initializing buffer pool, size = 8.0M
130702 3:14:54 InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 0 41789036
130702 3:14: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 42340688
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 0 372480
130702 3:14:55 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
InnoDB: Cleaning up trx with id 0 328576
130702 3:14:55 InnoDB: Rollback of non-prepared transactions completed
130702 3:14:55 InnoDB: Started; log sequence number 0 42340688
130702 3:14:55 [Note] Event Scheduler: Loaded 0 events
130702 3:14:55 [Note] mysqld: ready for connections.
Version: '5.1.66-0+squeeze1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
130702 3:14:56 InnoDB: Assertion failure in thread 2949757808 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3 341
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.htmlInnoDB: about forcing recovery.
10:14:56 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=16777216
read_buffer_size=131072
max_used_connections=0
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 = 345939 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 0x30000
mysqld(my_print_stacktrace+0x2d) [0xb753e8ad]
mysqld(handle_fatal_signal+0x4a4) [0xb7322e64]
[0xb6f6a400]
/lib/i686/cmov/libc.so.6(abort+0x182) [0xb6c8dbb2]
mysqld(fseg_free_step_not_header+0x203) [0xb742ccf3]
mysqld(+0x513a20) [0xb749ba20]
mysqld(+0x513f13) [0xb749bf13]
mysqld(trx_purge_fetch_next_rec+0x85) [0xb749c055]
mysqld(row_purge_step+0x42) [0xb747b912]
mysqld(que_run_threads+0x5b0) [0xb7466ea0]
mysqld(trx_purge+0x385) [0xb749a035]
mysqld(srv_master_thread+0xf80) [0xb7490330]
/lib/i686/cmov/libpthread.so.0(+0x5955) [0xb6f50955]
/lib/i686/cmov/libc.so.6(clone+0x5e) [0xb6d2c1de]
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.
Select Language