IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 44 and Version 45 of Replication_Issues


Ignore:
Timestamp:
Feb 22, 2012, 9:30:21 AM (14 years ago)
Author:
Serge CHASTEL
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Replication_Issues

    v44 v45  
    55
    66= 20120222/09:21: ippc19 =
    7 
     7Replication on ippc19 broke. The 'SHOW SLAVE STATUS\G' command showed the following message: {{{"Slave: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 0"}}}. /var/log/mysql/mysqld.err that replication was broken at log 'mysqld-bin.000639' position 1041257298 (see message {{{120222  8:46:23}}}). I stopped the slave, changed the master coordinates on the slave (with the input found in /var/log/mysql/mysqld.err) and restarted the slave, taht is:
     8{{{
     9STOP SLAVE;
     10CHANGE MASTER TO MASTER_LOG_FILE='mysqld-bin.000639',  MASTER_LOG_POS=1041257298;
     11START SLAVE;
     12}}}
     13Then "SHOW SLAVE STATUS\G" commands showed that replication worked again (Seconds_Behind_Master is decreasing).
    814= 20120203/08:51: ippc19  =
    915