[MDEV-19623] [ERROR] mysqld got signal 11 Created: 2019-05-28 Updated: 2019-08-19 Resolved: 2019-08-19 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 5.5.60 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | Nick Graham | Assignee: | Marko Mäkelä |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | crash, need_feedback | ||
| Environment: |
CentOS Linux release 7.6.1810 |
||
| Attachments: |
|
| Description |
|
I have a mariadb server that, for some reason, will no longer start. I've attached my entire mariadb.log file, but this seems to be the most relevant blob: 190528 13:32:48 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 20466 ... To report this bug, see http://kb.askmonty.org/en/reporting-bugs We will try our best to scrape up some info that will hopefully help Server version: 5.5.60-MariaDB Thread pointer: 0x0 |
| Comments |
| Comment by Marko Mäkelä [ 2019-06-25 ] |
|
Crackerjam, it would help if you could start the server under gdb, or do gdb -p $(pgrep mysqld) soon enough after starting the server. Alternatively, enable the core dump. The stack traces for all threads (thread apply all backtrace) would help narrow down the problem. Recently, |