maybe if you put on the slave server :
mysql> STOP SLAVE;
mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;
mysql> START SLAVE;
then just to check take a look at this lines :
mysql> show slave status\G;
...
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
...
it will restart the replication, but you have to check then why this happened,
just in case...
----- Original Message -----
From: Shain Miley
To: mysql@lists.mysql.com
Sent: Friday, January 09, 2009 3:17 PM
Subject: Mysql Replication out of sync
Hello all,
I noticed that my two Mysql slave servers were running out of sync this
morning. After looking into it...it appears that yesterday when I tried
to change the username of a user on the master server...it caused some
issues on the slaves. Here is what I was able to pull from the slave
error logs:
090108 16:46:05 [ERROR] Slave SQL: Error 'Operation CREATE USER failed
for 'root'@'127.0.0.1'' on query. Default database: 'mysql'. Query:
'CREATE USER 'root'@'127.0.0.1' IDENTIFIED BY PASSWORD
'*3313E27C7AD7F792A60D5D651029375E60'', Error_code: 1396
090108 16:46:05 [Warning] Slave: Operation CREATE USER failed for
'root'@'127.0.0.1' Error_code: 1396
090108 16:46:05 [ERROR] Error running query, slave SQL thread aborted.
Fix the problem, and restart the slave SQL thread with "SLAVE START". We
stopped at log 'master-bin.000008' position 970652826
Can anyone tell me if/how I can remove that statement from the log
file...so I can restart the slave?
Is there a better way to fix this?
Thanks,
Shain
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub=jb...@noticiasargentinas.com
__________ Información de NOD32, revisión 3749 (20090107) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com
