Description:
Mysql server crashes randomly. Have checked for other threads with similar problems, but for other threads, the common denominator seems to be myisam_use_mmap=1, which is not in my /etc/my.cnf file. The restart does require the databases to be repaired, and it's a painful process due to the large tables. I thought the upgrade to 5.1.58 would help, but it still randomly occurs.
---ERROR---
110725 18:32:56 - 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=10066329600
read_buffer_size=1048576
max_used_connections=443
max_threads=1024
threads_connected=87
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 12986712 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x760e370
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 = 0x489ccf08 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x85836e]
/usr/sbin/mysqld(handle_segfault+0x34f)[0x5c7c6f]
/lib64/libpthread.so.0[0x39c2e0eb10]
/usr/sbin/mysqld(_ZN11Query_cache27invalidate_query_block_listEP3THDP23Query_cache_block_table+0x1c)[0x6ddcdc]
/usr/sbin/mysqld(_ZN11Query_cache16invalidate_tableEP3THDPhj+0x3e)[0x6de3ee]
/usr/sbin/mysqld(_ZN11Query_cache16invalidate_tableEP3THDP10TABLE_LIST+0x48)[0x6de568]
/usr/sbin/mysqld(_ZN11Query_cache10invalidateEP3THDP10TABLE_LISTc+0x6d)[0x6de64d]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesb+0xae8)[0x652b78]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x142b)[0x5d3b8b]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x2ae)[0x5d8a9e]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x585)[0x5d9035]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xe4)[0x5da1b4]
/usr/sbin/mysqld(handle_one_connection+0x974)[0x5cc794]
/lib64/libpthread.so.0[0x39c2e0673d]
/lib64/libc.so.6(clone+0x6d)[0x39c1ed3d1d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2aad25476b60): is an invalid pointer
Connection ID (thread ID): 77544764
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.
110725 18:32:56 mysqld_safe Number of processes running now: 0
110725 18:32:56 mysqld_safe mysqld restarted
110725 18:32:56 [Warning] option 'max_relay_log_size': unsigned value 1572864000 adjusted to 1073741824
110725 18:32:58 [Note] Plugin 'FEDERATED' is disabled.
110725 18:32:58 InnoDB: Initializing buffer pool, size = 256.0M
110725 18:32:58 InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 358 2477337235
110725 18:32:58 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 358 2477345992
110725 18:32:59 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69
70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 530959729, file name ./mysql-bin.003666
110725 18:32:59 InnoDB: Started; log sequence number 358 2477345992
110725 18:32:59 [Note] Recovering after a crash using mysql-bin
110725 18:33:00 [Note] Starting crash recovery...
110725 18:33:00 [Note] Crash recovery finished.
110725 18:33:02 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.003724' at position 526426978, relay log './mysql-relay-bin.008220' position: 41376
110725 18:33:02 [Note] Slave I/O thread: connected to master 'repl@private:3306',replication started in log 'mysql-bin.003724' at position 526426978
110725 18:33:02 [Note] Event Scheduler: Loaded 0 events
110725 18:33:02 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.57-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
---
How to repeat:
Not sure how to repeat as it occurs at random, at no specific time.
Suggested fix:
Unsure.
