Bug #67713 MySQL crash
Submitted: 26 Nov 2012 16:37 Modified: 27 Dec 2012 19:22
Reporter: Stanimir Marinov Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: General Severity:S3 (Non-critical)
Version:mysql Ver 14.14 Distrib 5.5.28 OS:Linux (CentOS 64 bit)
Assigned to: CPU Architecture:Any

[26 Nov 2012 16:37] Stanimir Marinov
Description:
121124 18:25:09 [Warning] IP address '94.72.151.93' could not be resolved: Name or service not known
16:30:17 UTC - mysqld got signal 7 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=117
max_threads=151
thread_count=38
connection_count=37
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338489 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x3109e90
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 = 7fcb0b554d98 thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x78439e]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x66eed3]
/lib64/libpthread.so.0(+0xf500)[0x7fcc4ec1b500]
/usr/libexec/mysqld(_ZN3LEXC1Ev+0x496)[0x5755c6]
/usr/libexec/mysqld(_ZN7sp_head9reset_lexEP3THD+0x49)[0x7362c9]
/usr/libexec/mysqld(_Z10MYSQLparsePv+0x3b33)[0x637343]
/usr/libexec/mysqld(_Z9parse_sqlP3THDP12Parser_stateP19Object_creation_ctx+0x44)[0x579934]
/usr/libexec/mysqld[0x72e8bd]
/usr/libexec/mysqld[0x72fc11]
/usr/libexec/mysqld[0x730151]
/usr/libexec/mysqld(_Z16sp_cache_routineP3THDiP7sp_namebPP7sp_head+0xf1)[0x7302d1]
/usr/libexec/mysqld(_Z16sp_cache_routineP3THDP19Sroutine_hash_entrybPP7sp_head+0x71)[0x7303f1]
/usr/libexec/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0xa6d)[0x55157d]
/usr/libexec/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x47)[0x5518b7]
/usr/libexec/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbj+0x1e)[0x586f5e]
/usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x22ce)[0x5818be]
/usr/libexec/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1bb)[0x583d4b]
/usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1610)[0x585b10]
/usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0xd2)[0x614772]
/usr/libexec/mysqld(handle_one_connection+0x50)[0x614880]
/lib64/libpthread.so.0(+0x7851)[0x7fcc4ec13851]
/lib64/libc.so.6(clone+0x6d)[0x7fcc4d17211d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fcbc402c370): is an invalid pointer
Connection ID (thread ID): 9533858
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
121124 18:30:17 mysqld_safe Number of processes running now: 0
121124 18:30:17 mysqld_safe mysqld restarted

How to repeat:
I don`t know.
[27 Nov 2012 19:22] Sveta Smirnova
Thank you for the report.

Please try to find out which actions lead to this behavior.

You can find queries in general query log and update queries in the binary log if they are on. Please also send us your configuration file together with information of how much physical RAM do you have.
[28 Dec 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".