MySQL Forums
Forum List  »  Quality Assurance

mysqld got signal 11
Posted by: Tim Harvey
Date: February 04, 2013 11:08AM

The MySQL server crashed earlier and has logged a backtrace I'm just wondering if anyone is able to provide any insight into what may have been the cause of the crash please? It looke to me like it's something to do with query caching?

13:16:38 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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4382988 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x62685b0
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 = 7fa9580cbd98 thread_stack 0x40000

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

Options: ReplyQuote

Written By
mysqld got signal 11
February 04, 2013 11:08AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.