Keywords: MariaDB - Amazon Web Services - Technical issue - Other
Description:
Mariadb stopped working and the "mysqld.log" shows this:
What could be the problem?
2018-03-21 17:20:54 140393533602560 [Note] /opt/bitnami/mariadb/bin/mysqld.bin: Normal shutdown
2018-03-21 17:20:54 140393533602560 [Note] Event Scheduler: Purging the queue. 0 events
2018-03-21 17:20:54 140392544573184 [Note] InnoDB: FTS optimize thread exiting.
2018-03-21 17:20:54 140393533602560 [Note] InnoDB: Starting shutdown...
2018-03-21 17:20:55 140393533602560 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2018-03-21 17:20:56 140393533602560 [Note] InnoDB: Shutdown completed; log sequence number 13086635369
180321 17:20:56 [ERROR] mysqld got signal 7 ;
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 https://mariadb.com/kb/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: 10.1.29-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=20
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 = 467138 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 = 0x0 thread_stack 0x48400
/opt/bitnami/mariadb/bin/mysqld.bin(my_print_stacktrace+0x2e)[0xc182be]
/opt/bitnami/mariadb/bin/mysqld.bin(handle_fatal_signal+0x4bf)[0x77129f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7fafed0b5330]
/opt/bitnami/mariadb/bin/mysqld.bin(_ZN11TC_LOG_MMAP5closeEv+0x2a0)[0x844460]
/opt/bitnami/mariadb/bin/mysqld.bin[0x51d817]
/opt/bitnami/mariadb/bin/mysqld.bin(kill_server_thread+0x7b)[0x52434b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7fafed0ad184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fafebf89ffd]
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.
180321 17:20:56 mysqld_safe Number of processes running now: 0
180321 17:20:56 mysqld_safe mysqld restarted
2018-03-21 17:20:56 139878409897920 [Note] /opt/bitnami/mariadb/bin/mysqld.bin (mysqld 10.1.29-MariaDB) starting as process 21893 ...
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: Using Linux native AIO
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: Using SSE crc32 instructions
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: Completed initialization of buffer pool
2018-03-21 17:20:56 139878409897920 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-21 17:20:57 139878409897920 [Note] InnoDB: 128 rollback segment(s) are active.
2018-03-21 17:20:57 139878409897920 [Note] InnoDB: Waiting for purge to start
2018-03-21 17:20:57 139878409897920 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 13086635369
2018-03-21 17:20:57 139877354006272 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-03-21 17:20:57 139878409897920 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-21 17:20:57 139878409897920 [Note] Recovering after a crash using tc.log
2018-03-21 17:20:57 139878409897920 [ERROR] Can't init tc log
2018-03-21 17:20:57 139878409897920 [ERROR] Aborting
180321 17:20:59 mysqld_safe mysqld from pid file /opt/bitnami/mariadb/data/mysqld.pid ended
180321 17:45:17 mysqld_safe Starting mysqld daemon with databases from /opt/bitnami/mariadb/data
2018-03-21 17:45:19 139717476792256 [Note] /opt/bitnami/mariadb/bin/mysqld.bin (mysqld 10.1.29-MariaDB) starting as process 1380 ...
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: Using Linux native AIO
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: Using SSE crc32 instructions
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2018-03-21 17:45:19 139717476792256 [Note] InnoDB: Completed initialization of buffer pool
2018-03-21 17:45:20 139717476792256 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-21 17:45:20 139717476792256 [Note] InnoDB: 128 rollback segment(s) are active.
2018-03-21 17:45:20 139717476792256 [Note] InnoDB: Waiting for purge to start
2018-03-21 17:45:20 139717476792256 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 13086635379
2018-03-21 17:45:20 139716418561792 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-03-21 17:45:20 139717476792256 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-21 17:45:20 139717476792256 [Note] Recovering after a crash using tc.log
2018-03-21 17:45:20 139717476792256 [ERROR] Can't init tc log
2018-03-21 17:45:20 139717476792256 [ERROR] Aborting
180321 17:45:23 mysqld_safe mysqld from pid file /opt/bitnami/mariadb/data/mysqld.pid ended
180321 18:09:26 mysqld_safe Starting mysqld daemon with databases from /opt/bitnami/mariadb/data
2018-03-21 18:09:26 140565490100160 [Note] /opt/bitnami/mariadb/bin/mysqld.bin (mysqld 10.1.29-MariaDB) starting as process 1943 ...
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Using Linux native AIO
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Using SSE crc32 instructions
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Completed initialization of buffer pool
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: 128 rollback segment(s) are active.
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Waiting for purge to start
2018-03-21 18:09:26 140565490100160 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 13086635389
2018-03-21 18:09:26 140565490100160 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-21 18:09:26 140565490100160 [Note] Recovering after a crash using tc.log
2018-03-21 18:09:26 140565490100160 [ERROR] Can't init tc log
2018-03-21 18:09:26 140565490100160 [ERROR] Aborting
180321 18:09:29 mysqld_safe mysqld from pid file /opt/bitnami/mariadb/data/mysqld.pid ended
180321 18:16:00 mysqld_safe Starting mysqld daemon with databases from /opt/bitnami/mariadb/data
2018-03-21 18:16:00 140298874255296 [Note] /opt/bitnami/mariadb/bin/mysqld.bin (mysqld 10.1.29-MariaDB) starting as process 1284 ...
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Using Linux native AIO
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Using SSE crc32 instructions
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Completed initialization of buffer pool
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: 128 rollback segment(s) are active.
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Waiting for purge to start
2018-03-21 18:16:01 140298874255296 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 13086635399
2018-03-21 18:16:01 140297816205056 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-03-21 18:16:01 140298874255296 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-21 18:16:01 140298874255296 [Note] Recovering after a crash using tc.log
2018-03-21 18:16:01 140298874255296 [ERROR] Can't init tc log
2018-03-21 18:16:01 140298874255296 [ERROR] Aborting
180321 18:16:04 mysqld_safe mysqld from pid file /opt/bitnami/mariadb/data/mysqld.pid ended
AMI USED:
bitnami-mariadb-10.1.29-0-linux-ubuntu-14.04-x86_64-hvm-ebs-mp-669f6b18-405a-49a7-8be5-d018f1142489-ami-3323a849.4 (ami-0a62e273)
