MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:matthew zeier Date:May 28 2004 6:30am
Subject:replication problem, empty Binlog_do_db ?
View as plain text  
Running 4.0.20-standard-log on Fedora Core 1 on two boxes.  Running with a
largely untouched my-huge.cnf - innodb configs uncommented.


to setup replication.  On the master I see:

mysql> show master status;
| File        | Position | Binlog_do_db | Binlog_ignore_db |
| db2-bin.005 | 185      |              |                  |

The HOWTO seems to suggest that Binlog_do_db should have dbs I want to
replicate.  The slave seems forever stuck in:

*************************** 2. row ***************************
     Id: 2
   User: system user
     db: NULL
Command: Connect
   Time: 797
  State: Waiting for master to send event
   Info: NULL

Since I have InnoDB tables and don't have the money for InnoDB Hot Backup, I
did a 'flush tables with read lock; show master status' on the master,
shutdown the master and rsync'd /var/lib/mysql to the slave.  I started the
master back up, started the slave, ran the 'change master to' query and
started the slave.

Log shows:

040527 23:03:49  Slave SQL thread initialized, starting replication in log
'db2-bin.004' at position 211, relay log './db3-relay-bin.001' position: 4
040527 23:03:49  Slave I/O thread: connected to master 'dbslave@db2:3306',
replication started in log 'db2-bin.004' at position 211

and no other errors.  I have test.mrztest and can insert rows on the master
but they never appear on the slave.

Did I miss a step?  Is Binlog_do_db supposed to be empty?

matthew zeier - "Nothing in life is to be feared.  It is only to be
understood." - Marie Curie

replication problem, empty Binlog_do_db ?matthew zeier28 May