List:General Discussion« Previous MessageNext Message »
From:Michael T. Babcock Date:October 30 2002 6:16pm
Subject:Replication issue
View as plain text  
I'm replicating over a local SSH tunnel to a remote machine ... both 
MySQL instances have been working fine in the past (and both have their 
own binary logs, and only one database is being replicated between the 
two).  I'm getting this in the error logs:

021030 13:13:25  Slave: connected to master 'x@stripped:3303',  
replication started in log 'FIRST' at position 6281
021030 13:13:25  Slave: received 0 length packet from server, apparent 
master shutdown:
021030 13:13:25  Slave: Failed reading log event, reconnecting to retry, 
log 'FIRST' position 6281
021030 13:13:25  Slave: reconnected to master 
'x@stripped:3303',replication resumed in log 'FIRST' at position 6281
021030 13:13:25  Slave: received 0 length packet from server, apparent 
master shutdown:
021030 13:14:25  Slave: Failed reading log event, reconnecting to retry, 
log 'FIRST' position 6281

SSH is showing this:

debug1: Connection to port 3303 forwarding to 127.0.0.1 port 3306 requested.
debug1: fd 8 setting TCP_NODELAY
debug1: fd 8 setting O_NONBLOCK
debug1: channel 2: new [direct-tcpip]
debug1: channel 2: open confirm rwindow 131072 rmax 32768
debug1: channel 2: read<=0 rfd 8 len 0
debug1: channel 2: read failed
debug1: channel 2: close_read
debug1: channel 2: input open -> drain
debug1: channel 2: rcvd eof
debug1: channel 2: output open -> drain
debug1: channel 2: obuf empty
debug1: channel 2: close_write
debug1: channel 2: output drain -> closed
debug1: channel 2: ibuf empty
debug1: channel 2: send eof
debug1: channel 2: input drain -> closed
debug1: channel 2: send close
debug1: channel 2: rcvd close
debug1: channel 2: is dead
debug1: channel 2: garbage collecting
debug1: channel_free: channel 2: direct-tcpip: listening port 3303 for 
127.0.0.1 port 3306, connect from 127.0.0.1 port 1660, nchannels 3

-- 
Michael T. Babcock
C.T.O., FibreSpeed Ltd.
http://www.fibrespeed.net/~mbabcock


Thread
Replication issueMichael T. Babcock30 Oct