Skip to content

Instantly share code, notes, and snippets.

@paulschreiber

paulschreiber/gist:e4b7b63474ea9f8a8613

Created January 22, 2015 16:03
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save paulschreiber/e4b7b63474ea9f8a8613 to your computer and use it in GitHub Desktop.
Save paulschreiber/e4b7b63474ea9f8a8613 to your computer and use it in GitHub Desktop.
Download ZIP
MySQL crashlog
Raw
gistfile1.txt
150122 16:02:49 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150122 16:02:49 [Note] Plugin 'FEDERATED' is disabled.
150122 16:02:49 InnoDB: The InnoDB memory heap is disabled
150122 16:02:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150122 16:02:49 InnoDB: Compressed tables use zlib 1.2.3.4
150122 16:02:49 InnoDB: Initializing buffer pool, size = 128.0M
150122 16:02:49 InnoDB: Completed initialization of buffer pool
150122 16:02:49 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150122 16:02:49 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...
150122 16:02:49 InnoDB: Waiting for the background threads to start
150122 16:02:50 InnoDB: 5.5.40 started; log sequence number 608331920
150122 16:02:50 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150122 16:02:50 [Note] - '127.0.0.1' resolves to '127.0.0.1';
150122 16:02:50 [Note] Server socket created on IP: '127.0.0.1'.
150122 16:02:50 InnoDB: Assertion failure in thread 2759113536 in file trx0purge.c line 840
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:02:50 UTC - mysqld got signal 6 ;
150122 16:02:50 [Note] Event Scheduler: Loaded 0 events
150122 16:02:50 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.40-0ubuntu0.12.04.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
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 = 346075 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
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0xb731f3f3]
/usr/sbin/mysqld(handle_fatal_signal+0x484)[0xb71cb1e4]
[0xb6e7d400]
/usr/sbin/mysqld(+0x52f058)[0xb73cf058]
/usr/sbin/mysqld(+0x603bb9)[0xb74a3bb9]
/usr/sbin/mysqld(+0x5f980e)[0xb749980e]
/usr/sbin/mysqld(+0x5311d1)[0xb73d11d1]
/usr/sbin/mysqld(+0x520a2e)[0xb73c0a2e]
/usr/sbin/mysqld(+0x525321)[0xb73c5321]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb6dffd4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb6c0e8be]
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.
150122 16:02:51 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150122 16:02:51 [Note] Plugin 'FEDERATED' is disabled.
150122 16:02:51 InnoDB: The InnoDB memory heap is disabled
150122 16:02:51 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150122 16:02:51 InnoDB: Compressed tables use zlib 1.2.3.4
150122 16:02:51 InnoDB: Initializing buffer pool, size = 128.0M
150122 16:02:51 InnoDB: Completed initialization of buffer pool
150122 16:02:51 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150122 16:02: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...
150122 16:02:51 InnoDB: Waiting for the background threads to start
150122 16:02:52 InnoDB: 5.5.40 started; log sequence number 608331920
150122 16:02:52 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150122 16:02:52 [Note] - '127.0.0.1' resolves to '127.0.0.1';
150122 16:02:52 [Note] Server socket created on IP: '127.0.0.1'.
150122 16:02:52 [Note] Event Scheduler: Loaded 0 events
150122 16:02:52 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.40-0ubuntu0.12.04.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
150122 16:02:52 InnoDB: Assertion failure in thread 2758204224 in file trx0purge.c line 840
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:02: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=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 = 346075 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
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0xb72513f3]
/usr/sbin/mysqld(handle_fatal_signal+0x484)[0xb70fd1e4]
[0xb6daf400]
/usr/sbin/mysqld(+0x52f058)[0xb7301058]
/usr/sbin/mysqld(+0x603bb9)[0xb73d5bb9]
/usr/sbin/mysqld(+0x5f980e)[0xb73cb80e]
/usr/sbin/mysqld(+0x5311d1)[0xb73031d1]
/usr/sbin/mysqld(+0x520a2e)[0xb72f2a2e]
/usr/sbin/mysqld(+0x525321)[0xb72f7321]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb6d31d4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb6b408be]
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.
150122 16:02:53 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150122 16:02:53 [Note] Plugin 'FEDERATED' is disabled.
150122 16:02:53 InnoDB: The InnoDB memory heap is disabled
150122 16:02:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150122 16:02:53 InnoDB: Compressed tables use zlib 1.2.3.4
150122 16:02:53 InnoDB: Initializing buffer pool, size = 128.0M
150122 16:02:53 InnoDB: Completed initialization of buffer pool
150122 16:02:53 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150122 16:02: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...
150122 16:02:53 InnoDB: Waiting for the background threads to start
150122 16:02:54 InnoDB: 5.5.40 started; log sequence number 608331920
150122 16:02:54 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150122 16:02:54 [Note] - '127.0.0.1' resolves to '127.0.0.1';
150122 16:02:54 [Note] Server socket created on IP: '127.0.0.1'.
150122 16:02:54 [Note] Event Scheduler: Loaded 0 events
150122 16:02:54 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.40-0ubuntu0.12.04.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
150122 16:02:54 InnoDB: Assertion failure in thread 2758204224 in file trx0purge.c line 840
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:02: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=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 = 346075 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
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0xb73093f3]
/usr/sbin/mysqld(handle_fatal_signal+0x484)[0xb71b51e4]
[0xb6e67400]
/usr/sbin/mysqld(+0x52f058)[0xb73b9058]
/usr/sbin/mysqld(+0x603bb9)[0xb748dbb9]
/usr/sbin/mysqld(+0x5f980e)[0xb748380e]
/usr/sbin/mysqld(+0x5311d1)[0xb73bb1d1]
/usr/sbin/mysqld(+0x520a2e)[0xb73aaa2e]
/usr/sbin/mysqld(+0x525321)[0xb73af321]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb6de9d4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb6bf88be]
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment