070103 13:19:48 mysqld started InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 070103 13:19:48 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 070103 13:19:49 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 070103 13:19:49 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 070103 13:19:49 InnoDB: Started; log sequence number 0 0 070103 13:19:49 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.0.32-enterprise-gpl' socket: '/tmp/mysql2.sock' port: 3307 MySQL Enterprise Server (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=16384 read_buffer_size=258048 max_used_connections=1 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 31615 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x89b8c60 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=0xb38bc688, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8181f14 0x8160cca 0x81d27ee 0x81c53ed 0x81c637d 0x81c2115 0x8198cc7 0x827d5b2 0x827d3ce 0x827d4c8 0x827abf6 0x827b2e1 0x8287d65 0x81eb4a1 0x81977ed 0x819d4fe 0x81953b6 0x8194ec5 0x819455c 0xb7fb0504 0xb7eda51e 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 0x89bc410 = INSERT INTO fubar_changes (fubar_id, last_change_time) SELECT DISTINCT NEW.id AS fubar_id, NOW() AS last_change_time FROM fubar WHERE (id = NEW.id) AND ( (OLD.c != NEW.c) ) ON DUPLICATE KEY UPDATE last_change_time = IF ((fubar_id = NEW.id) AND ( (OLD.c != NEW.c) ) , NOW() , last_change_time) thd->thread_id=1 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. -e Number of processes running now: 0 070103 13:30:23 mysqld restarted 070103 13:30:23 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... 070103 13:30:23 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 43655. InnoDB: Doing recovery: scanned up to log sequence number 0 47350 070103 13:30:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 98 99 InnoDB: Apply batch completed 070103 13:30:24 InnoDB: Started; log sequence number 0 47350 070103 13:30:24 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.0.32-enterprise-gpl' socket: '/tmp/mysql2.sock' port: 3307 MySQL Enterprise Server (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=16384 read_buffer_size=258048 max_used_connections=1 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 31615 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x89b5f88 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=0xb51ef688, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8181f14 0x8160cca 0x81d27ee 0x81c53ed 0x81c637d 0x81c2115 0x8198cc7 Stack trace seems successful - bottom reached 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 0x89ef0b8 = INSERT INTO fubar_changes (fubar_id, last_change_time) SELECT DISTINCT NEW.id AS fubar_id, NOW() AS last_change_time FROM fubar WHERE (id = NEW.id) AND ( (OLD.c != NEW.c) ) ON DUPLICATE KEY UPDATE last_change_time = IF ((fubar_id = NEW.id) AND ( (OLD.c != NEW.c) ) , NOW() , last_change_time) 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. -e Number of processes running now: 0 070103 13:36:14 mysqld restarted 070103 13:36:14 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... 070103 13:36:14 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 51430. InnoDB: Doing recovery: scanned up to log sequence number 0 55852 070103 13:36:14 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 98 99 InnoDB: Apply batch completed 070103 13:36:15 InnoDB: Started; log sequence number 0 55852 070103 13:36:15 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.0.32-enterprise-gpl' socket: '/tmp/mysql2.sock' port: 3307 MySQL Enterprise Server (GPL)