Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.11.5
-
None
-
Not for Release Notes
Description
Hello Team
We have faced a DB crash at May 09, as checked in the mysqld.log, the DB got signal 11 (SIGSEGV) that's why it was restarted it could be a bug. see details below and the version of mariadb (see attached the complete logs)
250509 4:34:35 [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.
|
see below the version of mariadb and see attached the my.cnf file
MariaDB [aaadb]> select version();
|
+---------------------+
|
| version() |
|
+---------------------+
|
| 10.11.5-MariaDB-log |
|
+---------------------+
|
1 row in set (0.000 sec)
|
see below the /var/log/messages
May 9 04:42:49 ALEPO-DB1-ILB systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
|
May 9 04:42:49 ALEPO-DB1-ILB systemd[1]: mariadb.service: Failed with result 'signal'.
|
May 9 04:42:54 ALEPO-DB1-ILB systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
|
May 9 04:42:54 ALEPO-DB1-ILB systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 8.
|
May 9 04:42:54 ALEPO-DB1-ILB systemd[1]: Stopped MariaDB 10.11.5 database server.
|
May 9 04:42:54 ALEPO-DB1-ILB systemd[1]: Starting MariaDB 10.11.5 database server..
|
see attached also the core analysis by executing gdb core file
Attachments
Issue Links
- duplicates
-
-
- Closed
-