It's very strange because it only happens sometimes. Here is what i found in the error log:

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=16777216 read_buffer_size=258048 max_used_connections=354 max_connections=1000 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 780376 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.

thd=0xab06b928 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... Cannot determine thread, fp=0xa9b9bbd4, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x818282d 0xffffe420 0xf31acc8 0x8232edc 0x8232966 0x8236dd9 0x81bb699 0x81bc684 0x81b9622 0x8192f20 0x8198f97 0x8191ac2 0x81915bb 0x8190ca4 0xb7dc3aba 0xb7c3c1fe New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0xab44288 = SELECT *, `TABLE_SCHEMA` AS `Db`, `TABLE_NAME` AS `Name`, `ENGINE` AS `Engine`, `ENGINE` AS `Type`, `VERSION` AS `Version`, `ROW_FORMAT` AS `Row_format`, `TABLE_ROWS` AS `Rows`, `AVG_ROW_LENGTH` AS `Avg_row_length`, `DATA_LENGTH` AS `Data_length`, `MAX_DATA_LENGTH` AS `Max_data_length`, `INDEX_LENGTH` AS `Index_length`, `DATA_FREE` AS `Data_free`, `AUTO_INCREMENT` AS `Auto_increment`, `CREATE_TIME` AS `Create_time`, `UPDATE_TIME` AS `Update_time`, `CHECK_TIME` AS `Check_time`, `TABLE_COLLATION` AS `Collation`, `CHECKSUM` AS ` thd->thread_id=13100143 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash.

Number of processes running now: 0 060728 10:52:58 mysqld restarted 060728 10:52:58 [Warning] No argument was provided to --log-bin, and --lo ndex was not used; so replication may break when this MySQL server acts a ter and has his hostname changed!! Please use '--log-bin=myapi1-bin' to a is problem. 060728 10:52:58 InnoDB: Started; log sequence number 1 3405068341 060728 10:53:02 [Note] Recovering after a crash using myapi1-bin 060728 10:53:12 [Note] Starting crash recovery... 060728 10:53:12 [Note] Crash recovery finished. 060728 10:53:13 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.18-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Linux mysql-5.0.18

Jonathan Miller schrieb: