[MDEV-23873] [ERROR] mysqld got signal 11 ; Created: 2020-10-02 Updated: 2020-10-02 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Debug |
| Affects Version/s: | 10.3.24 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Stan | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | crash | ||
| Environment: |
CloudLinux 7.8, Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz, 128GB RAM, SSD storage. |
||
| Description |
|
Hello, It is the third time when on this server when we keep getting random high load average and mysql crash without any luck on finding whats causing the issue. The log show only: 201002 10:07:59 [ERROR] mysqld got signal 11 ; 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 Server version: 10.3.24-MariaDB-cll-lve Thread pointer: 0x0 |
| Comments |
| Comment by Daniel Black [ 2020-10-02 ] | ||||
|
is a core dump generated? Can you get a stack trace with: https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/#analyzing-a-core-file-with-gdb-on-linux ? | ||||
| Comment by Daniel Stan [ 2020-10-02 ] | ||||
|
Hello, We do not have a core file generated to be able to trace it with gdb though we have core_file inside the configuration. What do you suggest? | ||||
| Comment by Daniel Black [ 2020-10-02 ] | ||||
|
Any of these make sense in your environment https://mariadb.com/kb/en/enabling-core-dumps/? check /proc/$(pidof mysqld)/limits for the core limit of a running process. sysctl -a | grep core_ for kernel core dump settings. | ||||
| Comment by Daniel Stan [ 2020-10-02 ] | ||||
|
MariaDB [(none)]> SHOW GLOBAL VARIABLES LIKE 'core_file';
--------------
--------------
I do not see anything wrong except I cannot digg in more about it. |