CentOS - Feb 2009 - Problems with mysql multi-master after update.

Hello,

after I updated from mysql-5.0.22 CentOS 5.0 to mysqld-5.0.45 in CentOS 
5.2, mysql looses master-slave sync after one node reboots.
     I've noticed that the slave doest not respect the informantion on 
master.info, instead, it tries to read the informantion from the master 
server file inc-index.index.
     Let me give a example, the master is alredy on incremental.000006  
and the slave in synced, the master.info in the slave server is showing 
is is reading de incremental.000006, but in the master inc-index.index 
all 6 files are listed, from 1 to 6. The file 1 to 5 were already 
deleted in a cleaning process as thay were alread synced with the slave. 
After the reboot, the slave tries to find the file 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?

     Tks.

For what it's worth, I haven't seen this on any systems I manage when  
going from 5.0.22->5.0.45, which include permutations of master-slave  
and master-master.

Is there anything useful in /var/log/mysqld.log?

> after I updated from mysql-5.0.22 CentOS 5.0 to mysqld-5.0.45 in  
> CentOS
> 5.2, mysql looses master-slave sync after one node reboots.
>     I've noticed that the slave doest not respect the informantion on
> master.info, instead, it tries to read the informantion from the  
> master
> server file inc-index.index....

On Mon, Feb 9, 2009 at 7:33 AM, Alessandro Ren
<alessandro.ren at 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.

-- 
During times of universal deceit, telling the truth becomes a revolutionary act.
George Orwell