Code: Select all
key_buffer_size=16777216
read_buffer_size=1048576
max_used_connections=0
max_threads=70
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 = 231941 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb77b6500]
[0xb77b6420]
/lib/libc.so.6(gsignal+0x51)[0xb726d871]
/lib/libc.so.6(abort+0x17a)[0xb726f14a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb7799b39]
/lib/libc.so.6(clone+0x5e)[0xb7325c2e]
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.
151118 21:45:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151119 01:46:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151119 1:46:47 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151119 1:46:47 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 12504 ...
151119 1:46:47 [Note] Plugin 'FEDERATED' is disabled.
151119 1:46:47 InnoDB: The InnoDB memory heap is disabled
151119 1:46:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151119 1:46:47 InnoDB: Compressed tables use zlib 1.2.3
151119 1:46:47 InnoDB: Using Linux native AIO
151119 1:46:47 InnoDB: Initializing buffer pool, size = 128.0M
151119 1:46:47 InnoDB: Completed initialization of buffer pool
151119 1:46:47 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!
151119 1:46:47 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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151119 1:46:47 InnoDB: Waiting for the background threads to start
151119 1:46:48 InnoDB: 5.5.44 started; log sequence number 183581774
151119 1:46:48 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151119 1:46:48 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151119 1:46:48 [Note] Server socket created on IP: '0.0.0.0'.
151119 1:46:48 InnoDB: Assertion failure in thread 2743122800 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.
21:46: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=16777216
read_buffer_size=1048576
max_used_connections=0
max_threads=70
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 = 231941 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb77a9500]
[0xb77a9420]
/lib/libc.so.6(gsignal+0x51)[0xb7260871]
/lib/libc.so.6(abort+0x17a)[0xb726214a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb778cb39]
/lib/libc.so.6(clone+0x5e)[0xb7318c2e]
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.
151119 01:46:48 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 04:23:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 4:23:32 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 4:23:32 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 22260 ...
151121 4:23:32 [Note] Plugin 'FEDERATED' is disabled.
151121 4:23:32 InnoDB: The InnoDB memory heap is disabled
151121 4:23:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 4:23:32 InnoDB: Compressed tables use zlib 1.2.3
151121 4:23:32 InnoDB: Using Linux native AIO
151121 4:23:32 InnoDB: Initializing buffer pool, size = 128.0M
151121 4:23:32 InnoDB: Completed initialization of buffer pool
151121 4:23:32 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!
151121 4:23:32 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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 4:23:32 InnoDB: Waiting for the background threads to start
151121 4:23:33 InnoDB: 5.5.44 started; log sequence number 183581774
151121 4:23:33 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 4:23:33 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 4:23:33 [Note] Server socket created on IP: '0.0.0.0'.
151121 4:23:33 InnoDB: Assertion failure in thread 2743122800 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.
00:23:33 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=1048576
max_used_connections=0
max_threads=70
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 = 231941 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb77c2500]
[0xb77c2420]
/lib/libc.so.6(gsignal+0x51)[0xb7279871]
/lib/libc.so.6(abort+0x17a)[0xb727b14a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
151121 4:23:33 [Note] Event Scheduler: Loaded 0 events
151121 4:23:33 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.44' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb77a5b39]
/lib/libc.so.6(clone+0x5e)[0xb7331c2e]
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.
151121 04:23:33 mysqld_safe Number of processes running now: 0
151121 04:23:33 mysqld_safe mysqld restarted
151121 4:23:33 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 4:23:33 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 22298 ...
151121 4:23:33 [Note] Plugin 'FEDERATED' is disabled.
151121 4:23:33 InnoDB: The InnoDB memory heap is disabled
151121 4:23:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 4:23:33 InnoDB: Compressed tables use zlib 1.2.3
151121 4:23:33 InnoDB: Using Linux native AIO
151121 4:23:33 InnoDB: Initializing buffer pool, size = 128.0M
151121 4:23:33 InnoDB: Completed initialization of buffer pool
151121 4:23:33 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!
151121 4:23:33 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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 4:23:33 InnoDB: Waiting for the background threads to start
151121 4:23:34 InnoDB: 5.5.44 started; log sequence number 183581774
151121 4:23:34 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 4:23:34 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 4:23:34 [Note] Server socket created on IP: '0.0.0.0'.
151121 4:23:34 InnoDB: Assertion failure in thread 2743122800 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.
00:23:34 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=1048576
max_used_connections=0
max_threads=70
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 = 231941 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb778e500]
[0xb778e420]
/lib/libc.so.6(gsignal+0x51)[0xb7245871]
/lib/libc.so.6(abort+0x17a)[0xb724714a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb7771b39]
/lib/libc.so.6(clone+0x5e)[0xb72fdc2e]
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.
151121 04:23:34 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 18:19:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 18:19:15 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 18:19:15 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 28881 ...
151121 18:19:15 [Note] Plugin 'FEDERATED' is disabled.
151121 18:19:15 InnoDB: The InnoDB memory heap is disabled
151121 18:19:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 18:19:15 InnoDB: Compressed tables use zlib 1.2.3
151121 18:19:15 InnoDB: Using Linux native AIO
151121 18:19:15 InnoDB: Initializing buffer pool, size = 128.0M
151121 18:19:15 InnoDB: Completed initialization of buffer pool
151121 18:19:15 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!
151121 18:19: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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 18:19:15 InnoDB: Waiting for the background threads to start
151121 18:19:16 InnoDB: 5.5.44 started; log sequence number 183581774
151121 18:19:16 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 18:19:16 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 18:19:16 [Note] Server socket created on IP: '0.0.0.0'.
151121 18:19:16 InnoDB: Assertion failure in thread 2743122800 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.
14:19: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=16777216
read_buffer_size=1048576
max_used_connections=0
max_threads=20
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 = 77971 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb77b4500]
[0xb77b4420]
/lib/libc.so.6(gsignal+0x51)[0xb726b871]
/lib/libc.so.6(abort+0x17a)[0xb726d14a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb7797b39]
/lib/libc.so.6(clone+0x5e)[0xb7323c2e]
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.
151121 18:19:16 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 18:19:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 18:19:25 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 18:19:25 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 29595 ...
151121 18:19:25 [Note] Plugin 'FEDERATED' is disabled.
151121 18:19:25 InnoDB: The InnoDB memory heap is disabled
151121 18:19:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 18:19:25 InnoDB: Compressed tables use zlib 1.2.3
151121 18:19:25 InnoDB: Using Linux native AIO
151121 18:19:25 InnoDB: Initializing buffer pool, size = 128.0M
151121 18:19:25 InnoDB: Completed initialization of buffer pool
151121 18:19:25 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!
151121 18:19: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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 18:19:25 InnoDB: Waiting for the background threads to start
151121 18:19:26 InnoDB: 5.5.44 started; log sequence number 183581774
151121 18:19:26 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 18:19:26 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 18:19:26 [Note] Server socket created on IP: '0.0.0.0'.
151121 18:19:26 InnoDB: Assertion failure in thread 2743065456 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.
14:19:26 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=1048576
max_used_connections=0
max_threads=20
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 = 77971 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb771c500]
[0xb771c420]
/lib/libc.so.6(gsignal+0x51)[0xb71d3871]
/lib/libc.so.6(abort+0x17a)[0xb71d514a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb76ffb39]
/lib/libc.so.6(clone+0x5e)[0xb728bc2e]
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.
151121 18:19:26 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 18:20:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 18:20:25 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 18:20:25 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 30508 ...
151121 18:20:25 [Note] Plugin 'FEDERATED' is disabled.
151121 18:20:25 InnoDB: The InnoDB memory heap is disabled
151121 18:20:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 18:20:25 InnoDB: Compressed tables use zlib 1.2.3
151121 18:20:25 InnoDB: Using Linux native AIO
151121 18:20:25 InnoDB: Initializing buffer pool, size = 128.0M
151121 18:20:25 InnoDB: Completed initialization of buffer pool
151121 18:20:25 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!
151121 18:20: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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 18:20:25 InnoDB: Waiting for the background threads to start
151121 18:20:26 InnoDB: 5.5.44 started; log sequence number 183581774
151121 18:20:26 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 18:20:26 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 18:20:26 [Note] Server socket created on IP: '0.0.0.0'.
151121 18:20:26 InnoDB: Assertion failure in thread 2743122800 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.
14:20:26 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=1048576
max_used_connections=0
max_threads=20
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 = 77971 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb7744500]
[0xb7744420]
/lib/libc.so.6(gsignal+0x51)[0xb71fb871]
/lib/libc.so.6(abort+0x17a)[0xb71fd14a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb7727b39]
/lib/libc.so.6(clone+0x5e)[0xb72b3c2e]
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.
151121 18:20:26 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 18:22:35 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 18:22:35 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 18:22:35 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 1030 ...
151121 18:22:35 [Note] Plugin 'FEDERATED' is disabled.
151121 18:22:35 InnoDB: The InnoDB memory heap is disabled
151121 18:22:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 18:22:35 InnoDB: Compressed tables use zlib 1.2.3
151121 18:22:35 InnoDB: Using Linux native AIO
151121 18:22:35 InnoDB: Initializing buffer pool, size = 128.0M
151121 18:22:35 InnoDB: Completed initialization of buffer pool
151121 18:22:35 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!
151121 18:22: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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 18:22:35 InnoDB: Waiting for the background threads to start
151121 18:22:36 InnoDB: 5.5.44 started; log sequence number 183581774
151121 18:22:36 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 18:22:36 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 18:22:36 [Note] Server socket created on IP: '0.0.0.0'.
151121 18:22:36 InnoDB: Assertion failure in thread 2757925744 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.
14:22: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=1048576
read_buffer_size=1048576
max_used_connections=0
max_threads=20
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 = 62611 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb76ef500]
[0xb76ef420]
/lib/libc.so.6(gsignal+0x51)[0xb71a6871]
/lib/libc.so.6(abort+0x17a)[0xb71a814a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb76d2b39]
/lib/libc.so.6(clone+0x5e)[0xb725ec2e]
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.
151121 18:22:36 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 18:29:24 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 18:29:24 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 18:29:24 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 1765 ...
151121 18:29:24 [Note] Plugin 'FEDERATED' is disabled.
151121 18:29:24 InnoDB: The InnoDB memory heap is disabled
151121 18:29:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 18:29:24 InnoDB: Compressed tables use zlib 1.2.3
151121 18:29:24 InnoDB: Using Linux native AIO
151121 18:29:24 InnoDB: Initializing buffer pool, size = 128.0M
151121 18:29:24 InnoDB: Completed initialization of buffer pool
151121 18:29:24 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!
151121 18:29: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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 18:29:24 InnoDB: Waiting for the background threads to start
151121 18:29:25 InnoDB: 5.5.44 started; log sequence number 183581774
151121 18:29:25 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 18:29:25 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 18:29:25 [Note] Server socket created on IP: '0.0.0.0'.
151121 18:29:25 InnoDB: Assertion failure in thread 2758974320 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.
14:29: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=1048576
read_buffer_size=1048576
max_used_connections=0
max_threads=20
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 = 62611 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb778c500]
[0xb778c420]
/lib/libc.so.6(gsignal+0x51)[0xb7243871]
/lib/libc.so.6(abort+0x17a)[0xb724514a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb776fb39]
/lib/libc.so.6(clone+0x5e)[0xb72fbc2e]
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.
151121 18:29:25 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 18:59:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 18:59:08 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 18:59:08 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 2552 ...
151121 18:59:08 [Note] Plugin 'FEDERATED' is disabled.
151121 18:59:08 InnoDB: The InnoDB memory heap is disabled
151121 18:59:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 18:59:08 InnoDB: Compressed tables use zlib 1.2.3
151121 18:59:08 InnoDB: Using Linux native AIO
151121 18:59:08 InnoDB: Initializing buffer pool, size = 128.0M
151121 18:59:08 InnoDB: Completed initialization of buffer pool
151121 18:59:08 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!
151121 18:59: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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 18:59:08 InnoDB: Waiting for the background threads to start
151121 18:59:09 InnoDB: 5.5.44 started; log sequence number 183581774
151121 18:59:09 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 18:59:09 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 18:59:09 [Note] Server socket created on IP: '0.0.0.0'.
151121 18:59:09 InnoDB: Assertion failure in thread 2758974320 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.
14:59: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=1048576
read_buffer_size=1048576
max_used_connections=0
max_threads=20
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 = 62611 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb777b500]
[0xb777b420]
/lib/libc.so.6(gsignal+0x51)[0xb7232871]
/lib/libc.so.6(abort+0x17a)[0xb723414a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb775eb39]
/lib/libc.so.6(clone+0x5e)[0xb72eac2e]
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.
151121 18:59:09 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 19:12:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 19:12:07 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 19:12:07 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 4101 ...
151121 19:12:07 [Note] Plugin 'FEDERATED' is disabled.
151121 19:12:07 InnoDB: The InnoDB memory heap is disabled
151121 19:12:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 19:12:07 InnoDB: Compressed tables use zlib 1.2.3
151121 19:12:07 InnoDB: Using Linux native AIO
151121 19:12:07 InnoDB: Initializing buffer pool, size = 128.0M
151121 19:12:07 InnoDB: Completed initialization of buffer pool
151121 19:12:07 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!
151121 19:12: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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 19:12:07 InnoDB: Waiting for the background threads to start
151121 19:12:08 InnoDB: 5.5.44 started; log sequence number 183581774
151121 19:12:08 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 19:12:08 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 19:12:08 [Note] Server socket created on IP: '0.0.0.0'.
151121 19:12:08 InnoDB: Assertion failure in thread 2743122800 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.
15:12: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=16777216
read_buffer_size=1048576
max_used_connections=0
max_threads=200
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 = 632262 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb7747500]
[0xb7747420]
/lib/libc.so.6(gsignal+0x51)[0xb71fe871]
/lib/libc.so.6(abort+0x17a)[0xb720014a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb772ab39]
/lib/libc.so.6(clone+0x5e)[0xb72b6c2e]
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.
151121 19:12:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 19:12:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 19:12:39 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 19:12:39 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 4810 ...
151121 19:12:39 [Note] Plugin 'FEDERATED' is disabled.
151121 19:12:39 InnoDB: The InnoDB memory heap is disabled
151121 19:12:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 19:12:39 InnoDB: Compressed tables use zlib 1.2.3
151121 19:12:39 InnoDB: Using Linux native AIO
151121 19:12:39 InnoDB: Initializing buffer pool, size = 128.0M
151121 19:12:39 InnoDB: Completed initialization of buffer pool
151121 19:12:39 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!
151121 19:12: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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 19:12:40 InnoDB: Waiting for the background threads to start
151121 19:12:41 InnoDB: 5.5.44 started; log sequence number 183581774
151121 19:12:41 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 19:12:41 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 19:12:41 [Note] Server socket created on IP: '0.0.0.0'.
151121 19:12:41 InnoDB: Assertion failure in thread 2743122800 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.
15:12:41 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=1048576
max_used_connections=0
max_threads=200
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 = 632262 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb77e0500]
[0xb77e0420]
/lib/libc.so.6(gsignal+0x51)[0xb7297871]
/lib/libc.so.6(abort+0x17a)[0xb729914a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb77c3b39]
/lib/libc.so.6(clone+0x5e)[0xb734fc2e]
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.
151121 19:12:41 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151121 19:12:56 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151121 19:12:56 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151121 19:12:56 [Note] /usr/libexec/mysqld (mysqld 5.5.44) starting as process 5344 ...
151121 19:12:56 [Note] Plugin 'FEDERATED' is disabled.
151121 19:12:56 InnoDB: The InnoDB memory heap is disabled
151121 19:12:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151121 19:12:56 InnoDB: Compressed tables use zlib 1.2.3
151121 19:12:56 InnoDB: Using Linux native AIO
151121 19:12:56 InnoDB: Initializing buffer pool, size = 128.0M
151121 19:12:56 InnoDB: Completed initialization of buffer pool
151121 19:12:56 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!
151121 19:12:56 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: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4EA00
InnoDB: Cleaning up trx with id 4EA90
InnoDB: Cleaning up trx with id 4EA8A
151121 19:12:56 InnoDB: Waiting for the background threads to start
151121 19:12:57 InnoDB: 5.5.44 started; log sequence number 183581774
151121 19:12:57 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151121 19:12:57 [Note] - '0.0.0.0' resolves to '0.0.0.0';
151121 19:12:57 [Note] Server socket created on IP: '0.0.0.0'.
151121 19:12:57 InnoDB: Assertion failure in thread 2742074224 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.
15:12:57 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=1048576
max_used_connections=0
max_threads=200
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 = 632262 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/libexec/mysqld(my_print_stacktrace+0x34)[0x83effe4]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bdd0c]
[0xb7707500]
[0xb7707420]
/lib/libc.so.6(gsignal+0x51)[0xb71be871]
/lib/libc.so.6(abort+0x17a)[0xb71c014a]
/usr/libexec/mysqld[0x84b22a7]
/usr/libexec/mysqld[0x84b2890]
/usr/libexec/mysqld[0x857da3a]
/usr/libexec/mysqld[0x85734fe]
/usr/libexec/mysqld[0x84b0f59]
/usr/libexec/mysqld[0x84a2f56]
/usr/libexec/mysqld[0x84a7599]
/lib/libpthread.so.0(+0x6b39)[0xb76eab39]
/lib/libc.so.6(clone+0x5e)[0xb7276c2e]
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.
151121 19:12:57 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended