050420 7:25:17 [Note] Slave SQL thread initialized, starting replication in log 'mysql1-bin.000023' at position 222573736, relay log './mysql3-relay-bin.000024' position: 413221915 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=134217728 read_buffer_size=4190208 max_used_connections=2 max_connections=200 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1768670 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a9e2c0 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=0xbfe5ef18, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808ae43 0x82def78 0x80b6a03 0x80bae1f 0x812964f 0x812abc5 0x812ab0b 0x80d6172 0x80a0f01 0x809a8c9 0x809f3ff 0x80dea5d 0x81246b9 0x812541d 0x82dc72c 0x83060ba 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 0x44c6e59e is invalid pointer thd->thread_id=41106 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 050507 19:01:30 mysqld restarted 050507 19:01:30 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... 050507 19:01:30 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 236381376. InnoDB: Doing recovery: scanned up to log sequence number 0 236381376 InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 739282132, file name mysql1-bin.000033 InnoDB: Last MySQL binlog file position 0 79, file name ./mysql3-bin.000025 050507 19:01:31 InnoDB: Flushing modified pages from the buffer pool... 050507 19:01:31 InnoDB: Started; log sequence number 0 236381376 050507 19:01:31 [Note] Slave SQL thread initialized, starting replication in log 'mysql1-bin.000037' at position 260193316, relay log './mysql3-relay-bin.000038' position: 450844133 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=134217728 read_buffer_size=4190208 max_used_connections=0 max_connections=200 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1768670 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x891de10 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=0xbfe5ef18, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808ae43 0x82def78 0x80b6a03 0x80bae1f 0x812964f 0x812abc5 0x812ab0b 0x80d6172 0x80a0f01 0x809a8c9 0x809f3ff 0x80dea5d 0x81246b9 0x812541d 0x82dc72c 0x83060ba 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 0x8925b3e = /* * immissionen2mssql.sql * MeteoNews GmbH, Beat Vontobel, 2004-11-08 * * Kopiert die aktuellsten Immissions-Daten von met_data.nabel * nach MSSQL.immissionen, wird täglich um 19 UTC aufgerufen. * */ UPDATE MSSQL.immissionen, ( SELECT nabel.nabel_id AS id, ROUND(IFNULL(nabel.O3, -99)) AS o3, ROUND(IFNULL(nabel.NO2, -99)) AS no2, ROUND(IFNULL(nabel.SO2, -99)) AS so2, NOW()+0 AS bearbeitet FROM met_data.nabel WHERE nabel.date = ( SELECT MAX(date) FROM met_data.nabel) ) AS t SET immissionen.o3 = t.o3, immissionen.no2 = t.no2, immissionen.so2 = t.so2, immissionen.bearbeitet = t.bearbeitet WHERE immissionen.id = t.id thd->thread_id=2 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 050507 19:01:31 mysqld restarted 050507 19:01:31 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... 050507 19:01:31 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 236381376. InnoDB: Doing recovery: scanned up to log sequence number 0 236381410 InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 739282132, file name mysql1-bin.000033 InnoDB: Last MySQL binlog file position 0 79, file name ./mysql3-bin.000026 050507 19:01:31 InnoDB: Flushing modified pages from the buffer pool... 050507 19:01:31 InnoDB: Started; log sequence number 0 236381410 050507 19:01:32 [Note] Slave SQL thread initialized, starting replication in log 'mysql1-bin.000037' at position 260193316, relay log './mysql3-relay-bin.000038' position: 450844133 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=134217728 read_buffer_size=4190208 max_used_connections=0 max_connections=200 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1768670 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x891de10 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=0xbfe5ef18, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808ae43 0x82def78 0x80b6a03 0x80bae1f 0x812964f 0x812abc5 0x812ab0b 0x80d6172 0x80a0f01 0x809a8c9 0x809f3ff 0x80dea5d 0x81246b9 0x812541d 0x82dc72c 0x83060ba 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 0x8925b3e = /* * immissionen2mssql.sql * MeteoNews GmbH, Beat Vontobel, 2004-11-08 * * Kopiert die aktuellsten Immissions-Daten von met_data.nabel * nach MSSQL.immissionen, wird täglich um 19 UTC aufgerufen. * */ UPDATE MSSQL.immissionen, ( SELECT nabel.nabel_id AS id, ROUND(IFNULL(nabel.O3, -99)) AS o3, ROUND(IFNULL(nabel.NO2, -99)) AS no2, ROUND(IFNULL(nabel.SO2, -99)) AS so2, NOW()+0 AS bearbeitet FROM met_data.nabel WHERE nabel.date = ( SELECT MAX(date) FROM met_data.nabel) ) AS t SET immissionen.o3 = t.o3, immissionen.no2 = t.no2, immissionen.so2 = t.so2, immissionen.bearbeitet = t.bearbeitet WHERE immissionen.id = t.id thd->thread_id=2 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 050507 19:01:32 mysqld restarted 050507 19:01:32 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... 050507 19:01:32 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 236381410. InnoDB: Doing recovery: scanned up to log sequence number 0 236381444 InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 739282132, file name mysql1-bin.000033 InnoDB: Last MySQL binlog file position 0 79, file name ./mysql3-bin.000027 050507 19:01:32 InnoDB: Flushing modified pages from the buffer pool... 050507 19:01:32 InnoDB: Started; log sequence number 0 236381444 050507 19:01:33 [Note] Slave SQL thread initialized, starting replication in log 'mysql1-bin.000037' at position 260193316, relay log './mysql3-relay-bin.000038' position: 450844133 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=134217728 read_buffer_size=4190208 max_used_connections=0 max_connections=200 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1768670 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x891de10 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=0xbfe5ef18, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808ae43 0x82def78 0x80b6a03 0x80bae1f 0x812964f 0x812abc5 0x812ab0b 0x80d6172 0x80a0f01 0x809a8c9 0x809f3ff 0x80dea5d 0x81246b9 0x812541d 0x82dc72c 0x83060ba 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 0x8925b3e = /* * immissionen2mssql.sql * MeteoNews GmbH, Beat Vontobel, 2004-11-08 * * Kopiert die aktuellsten Immissions-Daten von met_data.nabel * nach MSSQL.immissionen, wird täglich um 19 UTC aufgerufen. * */ UPDATE MSSQL.immissionen, ( SELECT nabel.nabel_id AS id, ROUND(IFNULL(nabel.O3, -99)) AS o3, ROUND(IFNULL(nabel.NO2, -99)) AS no2, ROUND(IFNULL(nabel.SO2, -99)) AS so2, NOW()+0 AS bearbeitet FROM met_data.nabel WHERE nabel.date = ( SELECT MAX(date) FROM met_data.nabel) ) AS t SET immissionen.o3 = t.o3, immissionen.no2 = t.no2, immissionen.so2 = t.so2, immissionen.bearbeitet = t.bearbeitet WHERE immissionen.id = t.id thd->thread_id=2 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 050507 19:01:33 mysqld restarted 050507 19:01:33 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... 050507 19:01:33 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 236381444. InnoDB: Doing recovery: scanned up to log sequence number 0 236381478 InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 739282132, file name mysql1-bin.000033 InnoDB: Last MySQL binlog file position 0 79, file name ./mysql3-bin.000028 050507 19:01:33 InnoDB: Flushing modified pages from the buffer pool... 050507 19:01:33 InnoDB: Started; log sequence number 0 236381478 050507 19:01:33 [Note] Slave SQL thread initialized, starting replication in log 'mysql1-bin.000037' at position 260193316, relay log './mysql3-relay-bin.000038' position: 450844133