Crash mysqld segfault
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Incomplete
|
Undecided
|
Unassigned | |||
5.6 |
Incomplete
|
Undecided
|
Unassigned | |||
5.7 |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Percona Server 5.5.28-rel29.1 crashed unexpectedly.
There was enough RAM available, disks were OK, load was not extraordinary (about 2500 q/s).
System:
2x Xeon E5620
32 GB RAM
4x SAS 300GB SCSI in RAID10 (Areca 1212)
We've upgraded to 5.5.42-37.1, so I'm not able to perform any test anymore, but it seemed like a good idea to report it anyway.
As to me this seems like a segfault during an incoming network connection, I have tagged it as a security issue.
12:15:02 UTC - 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.
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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=500
thread_count=210
connection_
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x26fa7d20
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fd53f73aec0 thread_stack 0x40000
/usr/local/
/usr/local/
/lib64/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 192000064
Status: NOT_KILLED
information type: | Private Security → Public |
Please, send your my.cnf file content and (if possible) the output of pt-summary script from this host.
Is it possible that (reverse) DNS lookup did not work properly (or fast enough) when this crash happened?