MariaDB 10.3 crashing for no reason

Operating System & Version
Cloudlinux 7
cPanel & WHM Version
90.0.10

cybershubham

Registered
Jan 25, 2020
3
0
1
India
cPanel Access Level
Root Administrator
Hello,

This is happening after cPanel updates on one of my servers.

MariaDB 10.3 gets hung, also doesn't respond to chkservd.

The last time it happened 5 days ago..there was no error, the service status of MariaDB was Up & running - but all sites were getting database connection errors.

A quick restart resolved the problem. I thought it could be the DB Governor creating some problem - so I switched it to monitor mode only.

Today it happened again, Service status was UP but. The restart was not working today - it was simply getting hung from WHM and SSH as well.

I had to do a reboot and everything became normal.

This is all I got in my Logs:


Code:
200923 11:57:51 [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 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.3.24-MariaDB-cll-lve
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=46
max_threads=153
thread_count=52
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467439 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fa0ed412008

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...

This server is operational for several months and never caused any such problems.

The recent changes were:

1. Update to cPanel v11.90.0.10

2. Port 3306 was allowed recently in CSF firewall (I removed it today after the crash).


[[email protected] ~]# free -m
total used free shared buff/cache available
Mem: 15499 3074 1393 591 11032 10528
Swap: 0 0 0

[[email protected] ~]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.6G 0 7.6G 0% /dev
tmpfs 7.6G 49M 7.6G 1% /dev/shm
tmpfs 7.6G 18M 7.6G 1% /run
tmpfs 7.6G 0 7.6G 0% /sys/fs/cgroup
/dev/vda1 640G 400G 208G 66% /
/dev/loop0 3.9G 99M 3.6G 3% /tmp
tmpfs 1.6G 0 1.6G 0% /run/user/0

CPU Cores: 48

Please help me what could be the problem?
 

lfn

Registered
Sep 13, 2020
1
0
0
USA
cPanel Access Level
Website Owner
Hi,

I had a resent issue and for me it took 3 days to figure out. The DB locked/froze some tables on a cPanel update process in my case. But, in my case, it was a easy fix. Backup your DB before trying. Go to cPanel, Databases,and run the check database and see if you have any tables that show a error. Take a screenshot of those that do. Then, use the Repair Database button.



Let me know how this helps?
 

cPAdminsMichael

Well-Known Member
Dec 19, 2016
129
40
103
Denmark
cPanel Access Level
Root Administrator
I don't think it's directly related to a cPanel update as you are running MySQL Governor.
How does your my.cnf file look like? Also have you tried checking for corrupt tables?
 
  • Like
Reactions: cPanelLauren

andrew.n

Well-Known Member
Jun 9, 2020
328
71
28
EU
cPanel Access Level
Root Administrator
Do you see anything in "dmesg"? It's possible that it's being killed and the tables are getting corrupted and crashed as @cPAdminsMichael mentioned.
 

cybershubham

Registered
Jan 25, 2020
3
0
1
India
cPanel Access Level
Root Administrator
I don't think it's directly related to a cPanel update as you are running MySQL Governor.
How does your my.cnf file look like? Also have you tried checking for corrupt tables?
Hi, This is my.cnf:

Code:
[[email protected] ~]# cat /etc/my.cnf
[client-server]
!includedir /etc/my.cnf.d

[mysqld]
sql_mode = "ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
log-error = /var/lib/mysql/noida01.protondns.net.err
performance-schema = 0
innodb_file_per_table = 1
max_allowed_packet = 268435456
open_files_limit=80000
max_connections=1000
I had sent a ticket to the cPanel team - even they couldn't find a definite reason.
They recommended me to increase the RAM as the usage was very high around the time MariaDB was crashed, also recommended me to run repairs on a few crashed tables.

Now I have done that, let see if the issue comes again or not.