0

Hi I am trying import a mysql logical backup file on server A.Server A and B are in master slave configuration and both running on same unix server.slave is running while import is in progress.Due to heavy load on the server both master and slave are killed due to out of memory exception and restarted automatically by mysqld_safe. i have started the import process again on A but by stopping the slave in B to reduce the load on the unix server.import is successful on A. Later i have started the slave in mysql slave B . After some time slave B is crashed and below are the error log contents.

InnoDB: Assertion failure in thread 47225448184128 in file dict0dict.c line 2568  
InnoDB: Failing assertion: UT_LIST_GET_LEN(table->foreign_list) == 0  
InnoDB: We intentionally generate a memory trap.  
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.  
InnoDB: If you get repeated assertion failures or crashes, even  
InnoDB: immediately after the mysqld startup, there may be  
InnoDB: corruption in the InnoDB tablespace. Please refer to  
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html  
InnoDB: about forcing recovery.  
10:03:06 UTC - mysqld got signal 6 ;  
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=2097152  
max_used_connections=1  
max_threads=4000  
thread_count=0  
connection_count=0  

It is possible that mysqld could use up to  
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 49329259K  
bytes of memory Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1fc32d60  
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 = 2af388102ab8 thread_stack 0x40000  
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7de845]  
/usr/sbin/mysqld(handle_fatal_signal+0x3e1)[0x6956c1]  
/lib64/libpthread.so.0[0x2af2dc51cca0]  
/lib64/libc.so.6(gsignal+0x35)[0x2af2dd224fc5]  
/lib64/libc.so.6(abort+0x110)[0x2af2dd226a70]  
/usr/sbin/mysqld[0x87f48b]  
/usr/sbin/mysqld[0x887496]  
/usr/sbin/mysqld[0x890315]  
/usr/sbin/mysqld[0x89083a]  
/usr/sbin/mysqld[0x88cad1]  
/usr/sbin/mysqld[0x890508]  
/usr/sbin/mysqld[0x89083a]  
/usr/sbin/mysqld[0x88cad1]  
/usr/sbin/mysqld[0x884453]  
/usr/sbin/mysqld[0x888882]  
/usr/sbin/mysqld[0x889d08]  
/usr/sbin/mysqld[0x80a691]  
/usr/sbin/mysqld[0x7f23a3]  
/usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x149)[0x69bb79]  
/usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1ff)[0x60b50f]  
/usr/sbin/mysqld(_Z26mysql_create_table_no_lockP3THDPKcS2_P24st_ha_create_informationP10Alter_infobjPb+0x9ff)[0x5e0f3f]  
/usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xa1)[0x5e1aa1]  
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x5cb0)[0x582040]  
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10b)[0x58278b]  
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x10d9)[0x75b6a9]  
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x174)[0x518094]  
/usr/sbin/mysqld[0x51f9f9]  
/usr/sbin/mysqld(handle_slave_sql+0xd11)[0x520e61]  
/lib64/libpthread.so.0[0x2af2dc51483d]  
/lib64/libc.so.6(clone+0x6d)[0x2af2dd2c9fcd]  
Trying to get some variables.  
Some pointers may be invalid and cause the dump to abort.  

Query (2af380075088): CREATE TABLE `Tablename` (`p` datetime DEFAULT NULL,     
`q` datetime DEFAULT NULL,  
`r` int(11) NOT NULL,   
`s` int(11) NOT NULL, 
`t` int(11) NOT NULL,  
`u` int(11) NOT NULL,   
`v` tinyint(3) unsigned DEFAULT NULL,  
`w` varchar(100) COLLATE latin1_bin NOT NULL,  
UNIQUE KEY `idx_4817` (`s`,`w`),  
UNIQUE KEY `idx_5416` (`r`),  
KEY `fkey_4306` (`t`),   
CONSTRAINT `fkey_3694` FOREIGN KEY (`s`) REFERENCES `y` (`s`) ON DELETE NO   
ACTION ON UPDATE NO ACTION,    
CONSTRAINT `fkey_4306` FOREIGN KEY (`t`) REFERENCES `z` (`d`) ON DELETE NO   
ACTION ON UPDATE NO ACTION )   
ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_bin  
Connection ID (thread ID): 3  
Status: NOT_KILLED  

after this i can see crash recovery information in error log. Can any one help
me on this why crash occurred.

  • @RolandoMysqlDBA: can you check this once. – kasi May 19 '15 at 10:55
  • I am thinking FOREIGN_KEY_CHECKS=1 at the time of starting the slave in server B may result in this crash. i guess table y and z did not exist at that time. Any idea? – kasi Jun 19 '15 at 11:38
  • Can you relate crashes to this bug report of mysql 5.5 – mysql_user Jul 14 '15 at 5:50
  • getting file does not exist error..@mysql_user – kasi Jul 15 '15 at 6:33
  • @mysql_user:that link is not working – kasi Jul 15 '15 at 8:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.