help mariadb died

2 posts / 0 new
Last post
#1 Tue, 11/05/2019 - 19:02
dsoden
dsoden's picture

help mariadb died

This came with the default install of virtural min but the service is managed in webmin and wont start there so I am posting here. The service refuses to start and I have no clue where to even begin to resolve this as I have never seen this in 10 years of using MySQL/MariaDB.

‚óŹ mariadb.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-11-05 19:30:26 EST; 28min ago Process: 7663 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE) Process: 7662 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS) Process: 7627 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS) Main PID: 7662 (code=exited, status=0/SUCCESS)

///////// ABOUT MY SYSTEM Operating system CentOS Linux 7.7.1908 Webmin version 1.932
Usermin version 1.780 Virtualmin version 6.08
Authentic theme version 19.39-2 Kernel and CPU Linux 3.10.0-1062.4.1.el7.x86_64 on x86_64 Processor information Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz, 2 cores
Running processes 171 CPU load averages 0.39 (1 min) 0.17 (5 mins) 0.15 (15 mins) Real memory 739.38 MiB used / 841.23 MiB cached / 3.83 GiB total
Local disk space 8.84 GiB used / 28.88 GiB free / 37.72 GiB total Package updates All installed packages are up to date

///////// MARIADB LOG [root]# cat /var/log/mariadb/mariadb.log 191105 19:24:41 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 191105 19:24:41 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 5738 ... 191105 19:24:41 InnoDB: The InnoDB memory heap is disabled 191105 19:24:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins 191105 19:24:41 InnoDB: Compressed tables use zlib 1.2.7 191105 19:24:41 InnoDB: Using Linux native AIO 191105 19:24:41 InnoDB: Initializing buffer pool, size = 128.0M 191105 19:24:41 InnoDB: Completed initialization of buffer pool 191105 19:24:41 InnoDB: highest supported file format is Barracuda. 191105 19:24:41 InnoDB: Starting crash recovery from checkpoint LSN=813893419 InnoDB: Restoring possible half-written data pages from the doublewrite buffer... 191105 19:24:42 InnoDB: Starting final batch to recover 13 pages from redo log 191105 19:24:42 InnoDB: Waiting for the background threads to start 191105 19:24:42 InnoDB: Error: Write to file ./decisionforward/wp_postmeta.ibd failed at offset 0 622592. InnoDB: 16384 bytes should have been written, only 0 were written. InnoDB: Operating system error number 122. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 122 means 'Disk quota exceeded'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html 191105 19:24:42 InnoDB: Assertion failure in thread 139909834733312 in file os0file.c line 4380 InnoDB: Failing assertion: ret InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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. 191105 19:24:42 [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.64-MariaDB key_buffer_size=16777216 read_buffer_size=262144 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 = 136606 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 /usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x5630241679ad] /usr/libexec/mysqld(handle_fatal_signal+0x515)[0x563023d7b7b5] sigaction.c:0(__restore_rt)[0x7f3f7112c5f0] :0(__GI_raise)[0x7f3f6f854337] :0(__GI_abort)[0x7f3f6f855a28] /usr/libexec/mysqld(+0x717ac0)[0x563023ff1ac0] /usr/libexec/mysqld(+0x6c822d)[0x563023fa222d] /usr/libexec/mysqld(+0x6cdd46)[0x563023fa7d46] /usr/libexec/mysqld(+0x6d3ba3)[0x563023fadba3] /usr/libexec/mysqld(+0x668e20)[0x563023f42e20] /usr/libexec/mysqld(+0x738f0e)[0x563024012f0e] /usr/libexec/mysqld(+0x739bb8)[0x563024013bb8] /usr/libexec/mysqld(+0x72e477)[0x563024008477] /usr/libexec/mysqld(+0x63917d)[0x563023f1317d] /usr/libexec/mysqld(+0x62d0f6)[0x563023f070f6] pthread_create.c:0(start_thread)[0x7f3f71124e65] /lib64/libc.so.6(clone+0x6d)[0x7f3f6f91c88d] 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. 191105 19:24:42 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended 191105 19:30:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 191105 19:30:26 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 7933 ... 191105 19:30:26 InnoDB: The InnoDB memory heap is disabled 191105 19:30:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins 191105 19:30:26 InnoDB: Compressed tables use zlib 1.2.7 191105 19:30:26 InnoDB: Using Linux native AIO 191105 19:30:26 InnoDB: Initializing buffer pool, size = 128.0M 191105 19:30:26 InnoDB: Completed initialization of buffer pool 191105 19:30:26 InnoDB: highest supported file format is Barracuda. 191105 19:30:26 InnoDB: Starting crash recovery from checkpoint LSN=813893419 InnoDB: Restoring possible half-written data pages from the doublewrite buffer... 191105 19:30:26 InnoDB: Starting final batch to recover 13 pages from redo log 191105 19:30:26 InnoDB: Waiting for the background threads to start 191105 19:30:26 InnoDB: Error: Write to file ./decisionforward/wp_postmeta.ibd failed at offset 0 622592. InnoDB: 16384 bytes should have been written, only 0 were written. InnoDB: Operating system error number 122. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 122 means 'Disk quota exceeded'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html 191105 19:30:26 InnoDB: Assertion failure in thread 139981842544384 in file os0file.c line 4380 InnoDB: Failing assertion: ret InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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. 191105 19:30:26 [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.64-MariaDB key_buffer_size=16777216 read_buffer_size=262144 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 = 136606 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 /usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x560edf4839ad] /usr/libexec/mysqld(handle_fatal_signal+0x515)[0x560edf0977b5] sigaction.c:0(__restore_rt)[0x7f50353065f0] :0(__GI_raise)[0x7f5033a2e337] :0(__GI_abort)[0x7f5033a2fa28] /usr/libexec/mysqld(+0x717ac0)[0x560edf30dac0] /usr/libexec/mysqld(+0x6c822d)[0x560edf2be22d] /usr/libexec/mysqld(+0x6cdd46)[0x560edf2c3d46] /usr/libexec/mysqld(+0x6d3ba3)[0x560edf2c9ba3] /usr/libexec/mysqld(+0x668e20)[0x560edf25ee20] /usr/libexec/mysqld(+0x738f0e)[0x560edf32ef0e] /usr/libexec/mysqld(+0x739bb8)[0x560edf32fbb8] /usr/libexec/mysqld(+0x72e477)[0x560edf324477] /usr/libexec/mysqld(+0x63917d)[0x560edf22f17d] /usr/libexec/mysqld(+0x62d0f6)[0x560edf2230f6] pthread_create.c:0(start_thread)[0x7f50352fee65] /lib64/libc.so.6(clone+0x6d)[0x7f5033af688d] 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. 191105 19:30:26 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended

Tue, 11/05/2019 - 21:56
dsoden
dsoden's picture

corrupted DB removed and was able to bring up the server and restore db from backup

Best Regards,

.DS

Topic locked