List:Internals« Previous MessageNext Message »
From:Rick James Date:July 2 2009 6:54pm
Subject:FW: 5.1.30 crashes (sig 11)
View as plain text  

 
Rick James
MySQL Geeks - Consulting & Review

 
> I've received two of these mysqld crashes on two different servers  
> (within about 14 hours) in our new 5.1.30 production domain:
> 
> 090604 20:30:39 - 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.
> 
> key_buffer_size=2097152000
> read_buffer_size=131072
> max_used_connections=6
> max_threads=600
> threads_connected=2
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + 
> sort_buffer_size)*max_threads =  
> 41452503 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
> 
> thd: 0x7e26210
> 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 = 0x45250138 thread_stack 0x40000
> /home/y/libexec64/mysqld(my_print_stacktrace+0x26) [0x9c33c6]
> /home/y/libexec64/mysqld(handle_segfault+0x253) [0x62dd63]
> /lib64/tls/libpthread.so.0 [0x313320c5b0]
> /lib64/tls/libc.so.6(strlen+0x30) [0x3132570be0]
> /home/y/libexec64/mysqld(strdup_root+0x33) [0x9b14c3]
> /home/y/libexec64/mysqld(Query_arena::strdup(char const*)+0x21)  
> [0x57ff9f]
> /home/y/libexec64/mysqld(mysqld_list_processes(THD*, char 
> const*, bool) 
> +0x535) [0x761247]
> /home/y/libexec64/mysqld(mysql_execute_command(THD*)+0x2909) 
> [0x63d439]
> /home/y/libexec64/mysqld(mysql_parse(THD*, char const*, 
> unsigned int,  
> char const**)+0x17f) [0x6430ab]
> /home/y/libexec64/mysqld(dispatch_command(enum_server_command, THD*,  
> char*, unsigned int)+0x90d) [0x639669]
> /home/y/libexec64/mysqld(do_command(THD*)+0x13c) [0x638bd4]
> /home/y/libexec64/mysqld(handle_one_connection+0x128) [0x63767e]
> /lib64/tls/libpthread.so.0 [0x3133206137]
> /lib64/tls/libc.so.6(__clone+0x73) [0x31325c9883]
> Trying to get some variables.
> Some pointers may be invalid and cause the dump to abort...
> thd->query at 0x2bdff02940 is an invalid pointer
> thd->thread_id=678342
> thd->killed=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.
> 
> Any idea what might be going on?  Looks like it might be occurring  
> during simultaneous invocations of SHOW PROCESSLIST.
> 
> --Michael
> 
> 
Thread
FW: 5.1.30 crashes (sig 11)Rick James2 Jul 2009