Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Incomplete
-
5.5.60
-
CentOS Linux release 7.6.1810
Description
I have a mariadb server that, for some reason, will no longer start. I've attached my entire mariadb.log file, but this seems to be the most relevant blob:
190528 13:32:48 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 20466 ...
190528 13:32:48 InnoDB: The InnoDB memory heap is disabled
190528 13:32:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190528 13:32:48 InnoDB: Compressed tables use zlib 1.2.7
190528 13:32:48 InnoDB: Using Linux native AIO
190528 13:32:48 InnoDB: Initializing buffer pool, size = 128.0M
190528 13:32:48 InnoDB: Completed initialization of buffer pool
190528 13:32:48 InnoDB: highest supported file format is Barracuda.
190528 13:32:48 InnoDB: Starting crash recovery from checkpoint LSN=118221358827
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
190528 13:32:48 InnoDB: Starting final batch to recover 2229 pages from redo log
190528 13:32:48 [ERROR] mysqld got signal 11 ;
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.60-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 = 466718 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 0x48000
190528 13:32:48 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended