Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting

Replication still stopping

From: Jesse <jlc(at)msdlg.com>
Date: Sun Oct 21 2007 - 19:14:15 EDT


OK. Still battling this issue after weeks of working with it. I'm racking my brains. I re-set the slave again on Saturday, and got replication started again. It was working fine until this afternoon some time. Before starting things up, I cleaned the error log out completely, so it would be clean before I started. Here is my error log in total:

071020 14:43:51 InnoDB: Started; log sequence number 0 142497221 071020 14:43:51 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections. Version: '5.0.45-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
071020 14:43:51 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000006' at position 98, relay log 'C:\Program Files\MySQL\MySQL Server 5.0\Data\dlgsrv-relay-bin.000002' position: 235 071020 14:43:52 [Note] Slave I/O thread: connected to master
'Replication@webserver:3306', replication started in log 'mysql-bin.000006'
at position 98
071020 15:43:32 [Note] Slave: received end packet from server, apparent master shutdown:
071020 15:43:32 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000006' position 98 071020 15:43:33 [ERROR] Slave I/O thread: error reconnecting to master
'Replication@webserver:3306': Error: 'Can't connect to MySQL server on
'webserver' (10061)' errno: 2003 retry-time: 60 retries: 86400
071020 15:45:56 [Note] Slave: connected to master
'Replication@webserver:3306',replication resumed in log 'mysql-bin.000006'
at position 98
071021 15:02:21 [Note] Slave SQL thread exiting, replication stopped in log
'mysql-bin.000007' at position 195

I checked periodically on the server, and everything seemed to be working. The last time I checked was this morning sometime around 8:00 pr so. Still running. As you can see, however, it juststopped processing at 15:02:21 this afternoon.

The master server was not down. I was in and out of web sites that use the MySQL database on the master several times, and it always worked just fine, and never gave me an error. It almost appears as though the slave cannot communicate with the master. It looks like it tried 86,400 times, which I guess took almost a day to do, and just gave up. Why would it be able to connect initially to the server, then suddenly not be able to connect any more?

Any help or suggestions anyone can offer is greatly appreciated!

Jesse

-- 
MySQL Replication Mailing List
For list archives: 
http://lists.mysql.com/replication
To unsubscribe:    
http://lists.mysql.com/replication?unsub=lists@pantek.com
Received on Sun Oct 21 19:28:48 2007

This archive was generated by hypermail 2.1.8 : Fri Jul 04 2008 - 00:24:09 EDT


Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library