I'm exploring mysql replication under FreeBSD 4.2-RELEASE.

Two machines, named 'master' and 'slave', each running FreeBSD
4.2-RELEASE and MySQL 3.23.36-debug.

I've followed the instructions at

  <http://www.mysql.com/doc/R/e/Replication_HOWTO.html>

All very straight forward.

When I spin everything up, I see these errors on the slave server:

  /usr/local/libexec/mysqld: ready for connections

  010718 19:28:17  Slave: connected to master '[EMAIL PROTECTED]:3306',
  replication started in log 'FIRST' at position 4

  010718 19:29:22  Error reading packet from server: Lost connection
  to MySQL server during query (read_errno 35,server_errno=2013)

  010718 19:29:22  Slave: Failed reading log event, reconnecting
  to retry, log 'master-bin.001' position 803

  010718 19:29:22  Slave: reconnected to master
  '[EMAIL PROTECTED]:3306',replication resumed in log 'master-bin.001'
  at position 803

And the last two errors just keep repeating.  I can otherwise
connect just fine:

  slave% mysql -u repl -prepl -h master.xxx.xxx
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  Your MySQL connection id is 58 to server version: 3.23.36-debug-log
  
  Type 'help;' or '\h' for help. Type '\c' to clear the buffer
  
  mysql> quit
  Bye

I presume 'read_errno 35' refers to:

       35 EAGAIN Resource temporarily unavailable. This is a
       temporary condition and later calls to the same routine may
       complete normally.

Does anyone have any insight?  Funky hardware?  The list has mentioned 
4.2-RELEASE having threading problems, fixed in 4.3.  Might this be the
case?  I don't want to have to upgrade the OS, out-of-hand.

Upgrade the version of MySQL on the master a/o slave?  I see some
changes WRT replication:

  F.2.1 Changes in release 3.23.40
       
     Added slave_wait_timeout for replication. 
    
  F.2.3 Changes in release 3.23.38

     Better error message when slave max_allowed_packet is too low
     to read a very long log event from the master.

  F.2.4 Changes in release 3.23.37

     Fixed bug that erroneously logged a drop of internal temporary
     table on thread termination to the binary log - bug affected
     replication.

Would any of these apply to the errors I'm seeing?

-- 
Brian 'you Bastard' Reichert            <[EMAIL PROTECTED]>
37 Crystal Ave. #303                    Daytime number: (603) 434-6842
Derry NH 03038-1713 USA                 Intel architecture: the left-hand path

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to