replication-magic number-fire your magician

connecting to retry, log 'FIRST' position 4 010410 16:37:24 Slave: reconnected to master '[EMAIL PROTECTED]:3306',replication resumed in log 'FIRST' at position 4 010410 16:37:24 Error reading packet from server: Binlog has bad magic number, fire your magician (r

Re: bad magic number, fire your magician error

On Mon, Jun 25, 2001 at 06:52:34PM +, patrick ward wrote: > Hello Mr. Ziegler, > > I'm sorry if I'm intruding and promise not to do so again without your > consent but our db replication has come to a grinding halt with the error > 'bad magic number, fire y

Resolved {Was Re: Fire Your Magician}

> 010319 1:51:41 Error reading packet from server: Binlog has bad magic number, > > fire your magician (read_errno 0,server_errno=65535) > > 010319 1:51:41 Slave: Failed reading log event, reconnecting to retry, log > > 'FIRST' position 4 > > 010319 1

Re: Fire Your Magician

replication > resumed in log 'FIRST' at position 4 > 010319 1:51:41 Error reading packet from server: Binlog has bad magic number, > fire your magician (read_errno 0,server_errno=65535) > > Any thoughts would, obviously, be quite useful? > > BTW: The magician is me. So,

Fire Your Magician

This one's great: /usr/local/libexec/mysqld: ready for connections 010319 1:51:41 Slave: connected to master 'pima@scottsdale:3306', replication started in log 'FIRST' at position 4 010319 1:51:41 Error reading packet from server: Binlog has bad magic number, fire yo