Have you considered that a proxy server may be in the way. I have been 
watching this thread but I can't remember if you said anything about your 
network connectivity (sorry!). I have seen several programs make what they 
thought was a connection then fail because they don't know they are 
connecting through a proxy and not the real server. Also if your proxy is 
dropping your session, it could cause the same "interrupted" behavior. 

my 2 cents....

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine

matt ryan <[EMAIL PROTECTED]> wrote on 08/13/2004 08:58:43 AM:

> I reset the master, flush logs, reset master, show master status..
> 
> shows FINANCE-bin.186 at position 79
> 
> so I started the slave
> 
> 
> CHANGE MASTER TO
> MASTER_HOST='192.168.1.168',
> MASTER_USER='repl',
> MASTER_PASSWORD='Daredevil22',
> MASTER_LOG_FILE='FINANCE-bin.186',
> MASTER_LOG_POS=79;
> 
> start slave;
> 
> and I get this error after a few seconds..
> 
> 
> 040813  8:55:15  Slave SQL thread initialized, starting replication in 
> log 'FINANCE-bin.186' at position 79, relay log 
> '.\databasebackup-relay-bin.001' position: 4
> 040813  8:55:15  Slave I/O thread: connected to master 
> '[EMAIL PROTECTED]:3306',  replication started in log 'FINANCE-bin.186' 

> at position 79
> 040813  8:55:39  Error reading packet from server: binlog truncated in 
> the middle of event (server_errno=1236)
> 040813  8:55:39  Got fatal error 1236: 'binlog truncated in the middle 
> of event' from master when reading data from binary log
> 040813  8:55:39  Slave I/O thread exiting, read up to log 
> 'FINANCE-bin.186', position 79
> 
> 
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]
> 

Reply via email to