handle_fatal_signal in Item_func_case::cleanup()
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
New
|
Undecided
|
Unassigned |
Bug Description
Hello,
We're experiencing random Percona Server crashes. As this server handles 140+ databases, it's hard to identify what is causing this problem. Crashes seems to be very random. Sometimes occurs after few seconds, sometimes after many hours.
My OS is CentOS 6, kernel 2.6.32-
It crashes with such logs:
17:59:29 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=151
thread_count=42
connection_count=42
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: 0x7f55983154a0
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 = 7f56d81f0d40 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f55983d7aa0): is an invalid pointer
Connection ID (thread ID): 185464
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
Here's my my.cnf:
[mysqld]
pid-file=
log-error=
datadir=
socket=
user=mysql
skip-name-resolve
symbolic-links=0
ignore-db-dir = lost+found
slow_query_log = 1
slow_query_log_file = /var/log/
userstat = 1
wait_timeout = 7200
interactive_timeout = 7200
query_cache_limit = 64MB
max_heap_table_size = 64MB
key_buffer_size = 64MB
max_heap_table_size = 128MB
key_buffer_size = 128MB
query_cache_limit = 128MB
log_warnings = 2
tmp_table_size = 64MB
max_connections = 250
max_allowed_packet = 16M
max_connections = 150
max_heap_table_size = 64MB
key_buffer_size = 64MB
long_query_time = 10
[mysqld_safe]
log-error=
pid-file=
mysqlchech --all-databases took a while, but showed no errors.
The exact version of Percona: 5.7.18-14-log
Regards,
Konrad
I checked the error log excerpt against known bug strings, nothing there.