MySQL Forums
Forum List  »  Synchronization

Slave socket crashed and reboot
Posted by: greg rouf
Date: December 03, 2010 04:40AM

Hi,

I've set up a master-slave synchronisation between 2 mysql database. It looks like everything is working fine (both pointer are synchronized) but it doesn't properly. The slave seems to reboot every time he gets some data from the master.
Moreover it might be ok but when i do a "show master status" on the slave server, the pointer and the mysql-bin.0x file is changing all the time?! I tried to stop it through "stop master" with no effect.
After 3h, i got like 20 000 mysql-bin.0x files in my /var/log/mysql/.

Here some logs from Syslog:

101202 20:40:59 [Note] Slave I/O thread: connected to master 'user_slave@172.22.1.193:3306', replication started in log 'mysql-bin.000467' at position 63837695
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: Error: trying to access page number 17266432 in space 0,
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: space name ./ibdata1,
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: which is outside the tablespace bounds.
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: Byte offset 0, len 16384, i/o type 10.
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: If you get this error at mysqld startup, please check that
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: your my.cnf matches the ibdata files that you have in the
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: MySQL server.
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: 101202 20:41:00InnoDB: Assertion failure in thread 1141287264 in file fil0fil.c line 3959
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: We intentionally generate a memory trap.
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: If you get repeated assertion failures or crashes, even
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: immediately after the mysqld startup, there may be
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: InnoDB: about forcing recovery.
Dec 2 20:41:00 ORA-S-BK02 mysqld[20828]: mysqld got signal 11;


By the way I didn't specify any "binlog-do-db=" on the master, do we really need it if we use the bin-log ?

Many thanks in advance
Greg

Options: ReplyQuote


Subject
Views
Written By
Posted
Slave socket crashed and reboot
4557
December 03, 2010 04:40AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.