Maria Doesn't run

Virtualmin
1

Maria db doesn’t start virtualmin show me this mesagge
The full MariaDB error message was : DBI connect failed : Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (111 “Connection refused”)

web I try to start mariaDB server show me this error
Redirecting to /bin/systemctl start mariadb.service
Job for mariadb.service failed because a fatal signal was delivered to the control process. See “systemctl status mariadb.service” and “journalctl -xe” for details.

I Try systemctl status mariadb.service and whow me

[root@vmi353538 ~]# systemctl status mariadb.service
● mariadb.service - MariaDB 10.2.44 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor pre set: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: activating (auto-restart) (Result: signal) since Sun 2024-11-10 18:17 :00 CET; 176ms ago
Docs: man:mysqld(8)
systemd - MariaDB Knowledge Base
Process: 7838 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_N EW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
Process: 7821 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR = || VAR=cd /usr/bin/..; /usr/bin/galera_recovery; [ $? -eq 0 ] && systemc tl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/S UCCESS)
Process: 7819 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START _POSITION (code=exited, status=0/SUCCESS)
Main PID: 7838 (code=killed, signal=ABRT)

Nov 10 18:17:00 vmi353538.contaboserver.net systemd[1]: Failed to start Maria…
Nov 10 18:17:00 vmi353538.contaboserver.net systemd[1]: Unit mariadb.service …
Nov 10 18:17:00 vmi353538.contaboserver.net systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

and try journalctl -xe and show me

[root@vmi353538 ~]# journalctl -xe
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(+0x986681)[0x55a9f1f14681]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(+0x95611d)[0x55a9f1ee411d]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(+0x83dd2d)[0x55a9f1dcbd2d]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x55a9f1c3ace4]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(+0x526420)[0x55a9f1ab4420]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x9a2)[0x55a9f1ab5cf2]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(+0x471941)[0x55a9f19ff941]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x4be)[0x55a9f1a061be]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f9a46177555]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: /usr/sbin/mysqld(+0x46b61d)[0x55a9f19f961d]
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: information that should help you find out what is causing the crash.
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Writing a core file…
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Working directory at /var/lib/mysql
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Resource Limits:
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Limit Soft Limit Hard Limit Units
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max cpu time unlimited unlimited seconds
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max file size unlimited unlimited bytes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max data size unlimited unlimited bytes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max stack size 8388608 unlimited bytes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max core file size 0 unlimited bytes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max resident set unlimited unlimited bytes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max processes 63456 63456 processes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max open files 32768 32768 files
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max locked memory 65536 65536 bytes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max address space unlimited unlimited bytes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max file locks unlimited unlimited locks
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max pending signals 63456 63456 signals
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max msgqueue size 819200 819200 bytes
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max nice priority 0 0
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max realtime priority 0 0
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Max realtime timeout unlimited unlimited us
Nov 10 18:18:00 vmi353538.contaboserver.net mysqld[8816]: Core pattern: core
Nov 10 18:18:00 vmi353538.contaboserver.net systemd[1]: mariadb.service: main process exited, code=killed, status=6/ABRT
Nov 10 18:18:00 vmi353538.contaboserver.net systemd[1]: Failed to start MariaDB 10.2.44 database server.
– Subject: Unit mariadb.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit mariadb.service has failed.

– The result is failed.
Nov 10 18:18:00 vmi353538.contaboserver.net systemd[1]: Unit mariadb.service entered failed state.
Nov 10 18:18:00 vmi353538.contaboserver.net systemd[1]: mariadb.service failed.
Nov 10 18:18:02 vmi353538.contaboserver.net dovecot[1071]: pop3-login: Aborted login (auth failed, 1 attempts in 4 secs): user=root@hotelenbaqueira.com, method=PLAIN, r
Nov 10 18:18:02 vmi353538.contaboserver.net dovecot[1071]: pop3-login: Aborted login (auth failed, 1 attempts in 4 secs): user=root@hotelenbcn.com, method=PLAIN, rip=79
lines 1397-1442/1442 (END)

SYSTEM INFORMATION
OS type and version CentOS Linux 7.9.2009
Webmin version 2001
Virtualmin version 7.3
Webserver version REQUIRED
Related packages SUGGESTED
2

This is an end of life operating system I would suggest moving onto a virtualmin supported operating system. Not saying this is the issue but you will get more issues as your operating system is no longer maintained

3

Yes I have in track to migrate all to almalinux
But it worked for me until yesterday

4

The log entries you’ve posted are not the relevant ones we need to see. You’ve caught the tail end of the crash, but not the actual errors. You’ll want to use more specific queries to journalctl to find the problem.

You need to look at the actual errors. You might try starting it in safe mode so you can see the errors in their simplest form, or read the docs that the log entries you posted point you to: https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/

Or, you might want to start tailing the journal for the mariadb unit (journalctl -fu mariadb) and restart the service in another terminal. Then you can watch the whole start process in the log and see the relevant errors.

Mariadb is generally extremely reliable, so when it crashes, there’s probably something amiss on the system. Disk space (this can include quotas, though we try to protect against that, but if you’re using disk quotas and the database data directory is a filesystem using quotas, you might find that’s the cause), disk failure, memory problems, some other system problem. Check the kernel log (dmesg) for clues.

5

Thanks
This the mariadb.log → Dropbox

how should be the journalctl command to show the mariadb errors?
because if I launch it I get a lot of lines.

6 
2024-11-10 23:40:02 140452329683136 [ERROR] [FATAL] InnoDB: Trying to read page number 4294967295 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
241110 23:40:02 [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.

I don’t know what that error means, though (I’m not a Mariadb developer, and I’ve never seen this particular error).

I found this:

Note that in space 0 seems to be specific (there are lots of other reports of similar errors but in other space numbers…again, no idea what that means, but in space 0 seems like a different problem than in space 89 or whatever).

From what I can tell, what I said above remains true: It could be hardware failing, could be disk. You should do what I said above and check those things in addition (and maybe before) futzing around trying to fix the database. If you’re disk is failing or you’ve got bad memory or the kernel is crashing randomly, you probably won’t have much luck fixing software problems. Also make sure you’re not running out of disk space of have a full quota for a user with a database (if you’re using quotas and your database files are stored on a filesystem subject to quotas).

7

If its hardware you may need support from your provider.
Found this, not sure if it can help

1 Like
8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.