Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
We had a MariaDB 5.2.10 server that was continuously crashing:
{{{
Jan 17 16:17:07 server1 mysqld: 120117 16:17:07 [ERROR] mysqld got signal 11 ;
Jan 17 16:17:07 server1 mysqld: This could be because you hit a bug. It is also possible that this binary
Jan 17 16:17:07 server1 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Jan 17 16:17:07 server1 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Jan 17 16:17:07 server1 mysqld: We will try our best to scrape up some info that will hopefully help diagnose
Jan 17 16:17:07 server1 mysqld: the problem, but since we have already crashed, something is definitely wrong
Jan 17 16:17:07 server1 mysqld: and this may fail.
Jan 17 16:17:07 server1 mysqld:
Jan 17 16:17:07 server1 mysqld: key_buffer_size=0
Jan 17 16:17:07 server1 mysqld: read_buffer_size=131072
Jan 17 16:17:07 server1 mysqld: max_used_connections=17
Jan 17 16:17:07 server1 mysqld: max_threads=502
Jan 17 16:17:07 server1 mysqld: threads_connected=6
Jan 17 16:17:07 server1 mysqld: It is possible that mysqld could use up to
Jan 17 16:17:07 server1 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1098540 K
Jan 17 16:17:07 server1 mysqld: bytes of memory
Jan 17 16:17:07 server1 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Jan 17 16:17:07 server1 mysqld:
Jan 17 16:17:07 server1 mysqld: Thread pointer: 0x7fd61f517b70
Jan 17 16:17:07 server1 mysqld: Attempting backtrace. You can use the following information to find out
Jan 17 16:17:07 server1 mysqld: where mysqld died. If you see no messages after this, something went
Jan 17 16:17:07 server1 mysqld: terribly wrong...
Jan 17 16:17:07 server1 mysqld: stack_bottom = 0x2020202020202020 thread_stack 0x40000
Jan 17 16:17:07 server1 mysqld: *** glibc detected *** /usr/sbin/mysqld: malloc(): memory corruption: 0x00007fd62147d000 ***
}}}
Initially we thought this would be caused by hardware issues, but it's a repair of an archive table that triggers this. I've uploaded the table causing this crash to the FTP server.