-
Incident report
-
Resolution: Won't fix
-
Critical
-
None
-
2.4.6
-
None
-
Linux 7.0 VM
Unable to restart mysql (mariadb) DB after it crashed
Mariadb log attached
below is the log
[root@usczabbix00 mysql.march_18]# cat usczabbix00.err 160318 19:39:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 160318 19:39:03 InnoDB: The InnoDB memory heap is disabled 160318 19:39:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins 160318 19:39:03 InnoDB: Compressed tables use zlib 1.2.7 160318 19:39:03 InnoDB: Using Linux native AIO 160318 19:39:03 InnoDB: Initializing buffer pool, size = 128.0M 160318 19:39:03 InnoDB: Completed initialization of buffer pool 160318 19:39:03 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1275271120677 160318 19:39:03 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: Unable to lock ./zabbix/history_uint.ibd, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 160318 19:39:04 InnoDB: Assertion failure in thread 140391237220416 in file fil0fil.c line 859 InnoDB: Failing assertion: ret 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. 160318 19:39:04 [ERROR] 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. To report this bug, see http://kb.askmonty.org/en/reporting-bugs 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. Server version: 5.5.41-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=0 max_threads=153 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466712 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x0 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 = 0x0 thread_stack 0x48000 /usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7faf625ce79d] /usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7faf621e4475] /lib64/libpthread.so.0(+0xf130)[0x7faf61915130] /lib64/libc.so.6(gsignal+0x39)[0x7faf600cd5c9] /lib64/libc.so.6(abort+0x148)[0x7faf600cecd8] /usr/libexec/mysqld(+0x7561fc)[0x7faf6249b1fc] /usr/libexec/mysqld(+0x7563ec)[0x7faf6249b3ec] /usr/libexec/mysqld(+0x761671)[0x7faf624a6671] /usr/libexec/mysqld(+0x761701)[0x7faf624a6701] /usr/libexec/mysqld(+0x6e03f8)[0x7faf624253f8] /usr/libexec/mysqld(+0x7a091e)[0x7faf624e591e] /usr/libexec/mysqld(+0x6ca845)[0x7faf6240f845] /usr/libexec/mysqld(+0x68507c)[0x7faf623ca07c] /usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x7faf621e64f8] /usr/libexec/mysqld(+0x37c465)[0x7faf620c1465] /usr/libexec/mysqld(_Z11plugin_initPiPPci+0x559)[0x7faf620c71e9] /usr/libexec/mysqld(+0x2ee5fa)[0x7faf620335fa] /usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x546)[0x7faf620366e6] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7faf600b9af5] /usr/libexec/mysqld(+0x2e82dd)[0x7faf6202d2dd] 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. 160318 19:39:04 mysqld_safe mysqld from pid file /var/lib/mysql/usczabbix00.pid ended
- is duplicated by
-
ZBX-10555 Need help in start Zabbix DB
- Closed