On 2/11/2009 12:46 AM, Jim Perrin wrote:
On Mon, Feb 9, 2009 at 7:33 AM, Alessandro Ren
<alessandro....@opservices.com.br>  wrote:
e incremental.000001 on
the master and this causes the problem.
     In 5.0.22 this would not happen, this does not happen as I have
servers running this version and after the reboot, it starts syncing on
the right incremental.
     Any idea?


While I haven't seen this going from 0.22 to 0.45, did you run
mysql_upgrade following your upgrade?
Last I had this issue my table structure wasn't quite what the server
was expecting, and running mysql_upgrade was the solution.

    I tried it , but it did't help.
I just rebooted one of the nodes and I am getting this error in the logs. 090211 9:07:41 [ERROR] Failed to open the relay log '/var/run/mysqld/mysqld-relay-bin.000012' (relay_log_pos 358860475) 090211 9:07:41 [ERROR] Could not find target log during relay log initialization
090211  9:07:41 [ERROR] Failed to initialize the master info structure
090211  9:07:41 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.45-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution


Afeter deleting master.info and relay-log.ingo I get the incremental error:

090211 9:23:23 [ERROR] Error reading packet from server: File './incremental.000003' not found (Errcode: 2) ( server_errno=29) 090211 9:23:23 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'FIRST' position 4 090211 9:23:23 [Note] Slave: connected to master 'r...@192.168.10.207:3306',replication resumed in log 'FIRST' at position 4 090211 9:23:23 [ERROR] Error reading packet from server: File './incremental.000003' not found (Errcode: 2) ( server_errno=29)


After fixing de inc-index on the master en restarting, abd restarting the slave, it workis fine:

Version: '5.0.45-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 090211 9:26:14 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/run/mysqld/mysqld-relay-bin.000005' position: 98 090211 9:26:14 [Note] Slave I/O thread: connected to master 'r...@192.168.10.207:3306', replication started in log 'FIRST' at position 4


    Any tips? On 5.0.22 I never had this problem.

    Tks.




_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Reply via email to