Percona server crashes on Dell server

Bug #1101025 reported by KepPro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

The Percona server 5.5 crashes on Dell server R510 with this information:
Version: '5.5.25a-27.1-log' socket: '/data/mysql/mysql.sock' port: 3306 Percona Server (GPL), Release rel27.1, Revision 277
02:37:31 UTC - mysqld got signal 8 ;
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://bugs.percona.com/

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=4
max_threads=900
thread_count=3
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3730200 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2367eb80
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 = 7f846e618e58 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a8d05]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x685304]
/lib64/libpthread.so.0[0x367d20f500]
/usr/sbin/mysqld(_ZN12ha_partition21min_rows_for_estimateEv+0x61)[0x956f31]
/usr/sbin/mysqld(_ZN12ha_partition16records_in_rangeEjP12st_key_rangeS1_+0x35)[0x956f75]
/usr/sbin/mysqld[0x73cee7]
/usr/sbin/mysqld[0x73cc14]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f8448008ce0): is an invalid pointer
Connection ID (thread ID): 308
Status: NOT_KILLED
---------------------------------------------------------------------------------------------
Reducing max_connections from 900 to 500 didn't help: same error appeared (see the attached log)

Revision history for this message
KepPro (keppro) wrote :
Revision history for this message
KepPro (keppro) wrote :

Added the my.cnf

Revision history for this message
KepPro (keppro) wrote :
Revision history for this message
Vadim Tkachenko (vadim-tk) wrote :

This report looks like exactly like
https://bugs.launchpad.net/percona-server/+bug/1100984

Revision history for this message
Jervin R (revin) wrote :

I think I reported a bug upstream with the same behavior - I can see it is now private http://bugs.mysql.com/bug.php?id=65587

Do you have any partitioned tables by range without the MAXVALUE partition? Selecting for values beyond the biggest partition can cause this.

Revision history for this message
Alexey Kopytov (akopytov) wrote :

And exactly like bug #1033724. I think this has been fixed in 5.5.27 and higher versions. This apparently was fixed in 5.5.27, though the upstream bug report is private and I could not find anything related in release notes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.