[MDEV-9556] mysqld got signal 11 Created: 2016-02-14 Updated: 2016-03-15 Resolved: 2016-03-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | 5.5.47 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | olabi | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
centos 6.6 64bit , kernel 2.6.32-431.20.3.el6.x86_64 , 1 cpu 6 core , ram 16g , 1.1T external storage MSA 2040 FC |
||
| Description |
|
Dears, mysqld --print-defaults
Database down with the following error :
|
| Comments |
| Comment by Elena Stepanova [ 2016-02-15 ] |
|
Unfortunately, there is nothing to work with here. The readable part of the stack trace is very unspecific, server options show that you don't have general log enabled, and since it happened after 53 days, I assume it's not reproducible easily. I don't expect you know what kind of query the connection 26984798 could be executing, do you? If you can enable the general log in case it crashes again, it would be big help. For now we can suspect it's related to nearly any known bug, e.g. |
| Comment by Elena Stepanova [ 2016-03-15 ] |
|
Please comment to re-open if you have more information on the issue. |