Replication was running and is now "stuck" (1 reply)

Hi,

I'm hoping someone can help me. I have MYSQL replication running between a master and a new slave connected via a Internet VPN (The master has other slaves connected via LAN/VPN's which are all running fine).

Replication was running fine, although slowly and now seems to have stopped. Initially if I stopped the slave and restarted it, replication would run for a few minutes and stop but that no longer helps either.

If I do a show slave status everything seems fine,

Slave_IO_State: Waiting for master to send event
Slave_IO_Running: Yes
Slave_SQL_Running: Yes

I am however getting the following in my .err file.

00626 15:07:01 [Note] Slave: connected to master 'xxxx',replication resumed in log 'xxxx' at position xxxx
100626 15:13:07 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
100626 15:13:07 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'xxxx' position xxxx

Can anyone perhaps advise how I can resolve this? I have increased some of the timeouts as below. I have tested the connection between the master and slave and there is no packet loss, and I am getting a average of 600ms between the 2.

mysql> SHOW VARIABLES LIKE '%timeout%';
+----------------------------+-------+
| Variable_name | Value |
+----------------------------+-------+
| connect_timeout | 300 |
| delayed_insert_timeout | 300 |
| innodb_lock_wait_timeout | 50 |
| innodb_rollback_on_timeout | OFF |
| interactive_timeout | 28800 |
| net_read_timeout | 300 |
| net_write_timeout | 300 |
| slave_net_timeout | 3600 |
| table_lock_wait_timeout | 50 |
| wait_timeout | 28800 |