- Fri Jul 03, 2020 5:47 am
#828191
Recently we did a VMware conversion of our ProcessMaker server. After restarted the converted VM machine, mysql seems got problem to start, and mysql log shows InnoDB may be corrupted. The OS is CentOS 6, and mysql is ver 5.5. Currently mysql service is keep restarting itself, and we even cannot connect to mysql server in command line.
Here is the mysql log. This portion will keep repeating in the log. Thanks for any advice!
Here is the mysql log. This portion will keep repeating in the log. Thanks for any advice!
200703 17:39:28 [Note] Plugin 'FEDERATED' is disabled.
200703 17:39:28 InnoDB: The InnoDB memory heap is disabled
200703 17:39:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200703 17:39:28 InnoDB: Compressed tables use zlib 1.2.3
200703 17:39:28 InnoDB: Using Linux native AIO
200703 17:39:28 InnoDB: Initializing buffer pool, size = 128.0M
200703 17:39:28 InnoDB: Completed initialization of buffer pool
200703 17:39:28 InnoDB: highest supported file format is Barracuda.
200703 17:39:28 InnoDB: Waiting for the background threads to start
200703 17:39:29 InnoDB: 5.5.56 started; log sequence number 4487640042
200703 17:39:29 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
200703 17:39:29 [Note] - '0.0.0.0' resolves to '0.0.0.0';
200703 17:39:29 [Note] Server socket created on IP: '0.0.0.0'.
200703 17:39:29 [Note] Event Scheduler: Loaded 0 events
200703 17:39:29 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.56' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
200703 17:39:29 InnoDB: Assertion failure in thread 140517736490752 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.
09:39: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=8388608
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 = 338509 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+0x2e)[0x79006e]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x678203]
/lib64/libpthread.so.0[0x37c500f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x37c4c32495]
/lib64/libc.so.6(abort+0x175)[0x37c4c33c75]
/usr/libexec/mysqld[0x8269e4]
/usr/libexec/mysqld[0x826e57]
/usr/libexec/mysqld[0x8e4c0f]
/usr/libexec/mysqld[0x8daf95]
/usr/libexec/mysqld[0x8256a5]
/usr/libexec/mysqld[0x8188dc]
/usr/libexec/mysqld[0x81ca23]
/lib64/libpthread.so.0[0x37c5007aa1]
/lib64/libc.so.6(clone+0x6d)[0x37c4ce8bcd]
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.
- By domnickfury
- By Kiruthikaa