I posted this message on the Replication list, but have got no responses,
so, I figured I'd try here.
I just set up Replication recently with a Web Server 2003 server being the
master and a Windows 2000 server machine being the slave. When I got done, I
did a few tests, and all appeared to be fine. Sunday Morning, I checked the
event logs on the slave machine, and there was an entry in there that said
"Slave SQL thread exiting, replication stopped in log 'mysql-bin.000001' at
position 190" this occurred almost exactly 2 hours after I had finished
setting up the slave.
I checked, and sure enough, replication no longer appeared to be working
when I tried to change a value on the master, it did not seem to replicate
to the slave (yes, I realize there can be some time delay, but the machines
were not busy at all).
I did a SHOW SLAVE STATUS on the slave, and it came back with "Waiting for
master to send event". But, it wasn't not working. So, I stopped the MySQL
Server on the slave machine, and re-started it. It seemed to start alright,
but immediately gave an error in the event log about a foreign key
violation. I "re-sync'd" that database (I'm going to post a separate message
about that), and continued on.
I checked again this morning (Monday),and it appears to have stopped again,
because some new records that were added to the master have not been added
to the slave.
My question is this; What caused the slave to just stop replicating? There
was no explanation at all that I could tell.
Thanks,
Jesse
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
