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:
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?
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?
