050829 08:47:05 mysqld started 050829 8:47:06 InnoDB: Started; log sequence number 0 617780726 /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.1.14-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 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=536870912 read_buffer_size=2093056 max_used_connections=48 max_connections=300 threads_connected=42 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1751885 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x65a1c8c8 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=0xbfddeb78, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808cb93 0x82e4c18 0x82d1d90 0x80b7fe0 0x80b826f 0x804ea90 0x805666a 0x80b92e5 0x80bd363 0x80c009f 0x80d9422 0x809e46d 0x80a1437 0x809b73e 0x809b108 0x809a7d7 0x82e23cc 0x830bd5a 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 0x65204da0 is invalid pointer thd->thread_id=41172 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 050830 01:16:20 mysqld restarted 050830 1:16:20 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... 050830 1:16:20 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 617781978. InnoDB: Doing recovery: scanned up to log sequence number 0 617781978 InnoDB: Last MySQL binlog file position 0 205363910, file name ./mysql1-bin.000133 050830 1:16:20 InnoDB: Flushing modified pages from the buffer pool... 050830 1:16:20 InnoDB: Started; log sequence number 0 617781978 /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.1.14-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 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=536870912 read_buffer_size=2093056 max_used_connections=81 max_connections=300 threads_connected=27 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1751885 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x6527b290 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=0xbfd9edc8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808cb93 0x82e4c18 0x804d158 0x804ef82 0x80b8c2b 0x80bd2f8 0x80c009f 0x80bd1a6 0x809e742 0x80a1437 0x809b73e 0x809b108 0x809a7d7 0x82e23cc 0x830bd5a 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 0x8c15610 = REPLACE INTO met_data.metar_archive (id, datetime, dd, ff, fxx, tt, td, rh, vis, ppnn, cld_okt, cld_hgt, ceiling, prcp_type, prcp_str, flags, wx) SELECT id, datetime, dd, ff, fxx, tt, td, rh, vis, ppnn, cld_okt, cld_hgt, ceiling, prcp_type, prcp_str, flags, wx FROM metar WHERE id = 'AYMO' thd->thread_id=464605 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 050906 01:15:55 mysqld restarted 050906 1:15:55 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... 050906 1:15:56 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 617788220. InnoDB: Doing recovery: scanned up to log sequence number 0 617788220 InnoDB: Last MySQL binlog file position 0 4, file name ./mysql1-bin.000138 050906 1:15:56 InnoDB: Flushing modified pages from the buffer pool... 050906 1:15:56 InnoDB: Started; log sequence number 0 617788220 /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.1.14-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 050906 10:33:59 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown 050906 10:34:02 InnoDB: Starting shutdown... 050906 10:34:05 InnoDB: Shutdown completed; log sequence number 0 617788650 050906 10:34:05 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete 050906 10:34:05 mysqld ended 050906 10:34:05 mysqld started 050906 10:34:06 InnoDB: Started; log sequence number 0 617788650 /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.1.13-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)