> Hi,
>
> on server B you need to set log-slave-updates to pass statements from
A
> over B to D.
>
> BTW: I can recommend you to use replicate-wild-do-table=db_name.*
> instead of replicate-do-db, otherwise statements with db prefix before
> tables won't replicate over B to D. RTM please
>
>
>
> You should have:
> log-slave-updates
>
> on the slave/master host(s)
>
>
> Best regards,
> Irek Slonina
Irek,
Thanks for the follow up. Someone else has mentioned it but I just noticed
that it was offlist.
Hi,
on server B you need to set log-slave-updates to pass statements from A
over B to D.
BTW: I can recommend you to use replicate-wild-do-table=db_name.*
instead of replicate-do-db, otherwise statements with db prefix before
tables won't replicate over B to D. RTM please
Filip
I'm wor
I'm working with two distinct databases on four different boxes.
Databases A on Server A needs to be present everywhere (Server B, C and
D). Database B needs to be present on Server C.
So I setup replication from Server A to Server B and Server D and then I
setup replication from Server B to Serv
_db:
Last_errno: 0
Last_error:
Skip_counter: 0
Exec_master_log_pos: 551
Relay_log_space: 45
1 row in set (0.02 sec)
mysql>
On Jun 25, 2004, at 1:41 AM, Rousseau, Pierre wrote:
Re: Master Slave Problem :
mysql> show slave status\G
*
Re: Master Slave Problem :
mysql> show slave status\G
*** 1. row ***
Master_Host: 164.23.43.160
Master_User: Replikator
Master_Port: 3306
Connect_retry: 60
Master_Log_File:
Read_Master_Log_Pos: 1
Log into the slave and do this command
mysql> mysql> show slave status\G
. what do you see?
Also, what is in your my.cnf file on the slave?
FYI, here is instructions on how I set up replication last week
http://homepage.mac.com/kelleherk/iblog/C711669388/E351220100/index.html
-Kieran
__
Hi Bug Team,
I have set up a Master Slave System with MySQL 4.0.20. I've done completing every task
from "6.4 How to Set Up Replication".
But my problem is :
040624 14:44:44 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306',
replication started in log 'FIRST' at position 4
0406
