Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.4.12
-
Test
Description
cluster status in kubernetes is giving error and we see the db is down due to bug message shown in error. Kindly check the attached logs and revert.
4 11:30:24 [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.
Attachments
Issue Links
- relates to
-
MDEV-13542 Crashing on a corrupted page is unhelpful
-
- Closed
-
InnoDB can add 100 or 200 to the original error code. The command
perror 5
tells me the following:
OS error code 5: Input/output error
Please check for any errors in
sudo dmesg
sudo smartctl -a /dev/sda
and other logs. Yes, as reported in
MDEV-13542, InnoDB could handle theses better.The stack trace in mariadblogs crash.txt
is not resolved. Please try to follow https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ and provide a resolved stack trace.