RE: Replication problem Timeout in MySQL

2002-06-14 Thread Sbastien DIDIER
Ok. So i'm a bit confused with all the timeout values. My replication process is killed because of a net_read_timeout which is 30 secondes . I think there's at least three different timeouts : net_read_timeout : The process will be killed if it doesn't receive data during net_read_timeout secs.

Re: replication problem

2002-06-06 Thread Frederic Dhorne
Hi, I already had a similar problem. I did the following things: I zipped my master database to unzip it on the slave and then I did a reset master,that's it. The reason why you have this problem it's certainly due to the fact that your master and slave database are not identical. you didn't

RE: replication problem

2002-06-03 Thread Terry
Hello, More than likely you have missed the step that the slave database has to be the exact one that the master has before the start of the binlog. Shutdown both servers, grab a copy of the master's data directory and tar that up, move that to the slave, delete the slave's current data

Re: replication problem

2002-05-31 Thread Scott Helms
More than likely you have missed the step that the slave database has to be the exact one that the master has before the start of the binlog. Shutdown both servers, grab a copy of the master's data directory and tar that up, move that to the slave, delete the slave's current data directory, now

Re: Replication problem

2002-05-27 Thread Benjamin Pflugmann
Hi. As I have seen no answer yet, just a wild guess: Maybe you have some query which used both databases, something like INSERT INTO fdf.whatever SELECT FROM access.pagespromo ... You can always use the binlog utilities and have a look at the query which caused the failure. Regards,

Re: Replication Problem

2002-05-10 Thread Terrence Cox
Hi Raymond, That's an interesting message you're getting. Obviously there is an issue with IP address not getting to mysqld. The only thing that can make any sense to me in this one is double check the name and location of the my.cnf file. See ya, Terrence - Original Message - From:

RE: Replication Problem

2002-05-10 Thread Luc Foisy
btw, things look much prettier if you use show slave status\G the replicant user, and host ip address does not match your my.cnf on the slave master-host=20.0.0.54 master-user=echo | Master_Host | Master_User | Master_Port | Connect_retry | Log_File | Pos | | | test| 3306

RE: Replication Problem

2002-05-10 Thread Luc Foisy
actually you may want to change [MYSQLD] to [mysqld] and restart your slave server I don't think it has read your my.cnf file correctly ( that means the other settings will not have taken affect either, like password and server ID) -Original Message- From: Raymond Brighenti

RE: Replication Problem

2002-05-10 Thread Raymond Brighenti
wouldn't be able to use it as a slave otherwise. Very strange, any other things to try? Ray -Original Message- From: Luc Foisy [mailto:[EMAIL PROTECTED]] Sent: 10 May 2002 2:24 To: 'Raymond Brighenti'; MYSQL-List (E-mail) Subject: RE: Replication Problem actually you may want to change

RE: Replication Problem

2002-05-10 Thread Luc Foisy
PROTECTED]' Subject: RE: Replication Problem Hi, I tried using a FreeBSD box with MySQL as the Master and W2K as the slave and it works fine. I then swapped it so the W2K was master and I get the following from the Unix box. 020510 14:14:22 mysqld started /usr/local/libexec/mysqld: ready

Re: Replication Problem

2002-05-10 Thread Jeremy Zawodny
On Fri, May 10, 2002 at 10:23:30AM +0100, Raymond Brighenti wrote: Hi, Trying to get replication going between to W2K machines and getting the following errors in the Slave log file. MySql: ready for connections 020509 18:58:52 Slave thread: error connecting to master:Can't connect to

Re: Replication problem

2002-02-01 Thread Hery Yulianto
my solution for this problem 1. Please you look status salve on the mysql with syntax mysql show slave status 2. After that, please you look Log_File on column, what a name file ? 3. Please you open your shell this file with mysqlbinlog file_name | more 4. please you find the position

Re: Replication Problem on MySQL 3.23.45/Win32

2001-12-10 Thread A. Clausen
07, 2001 21:41 Subject: Re: Replication Problem on MySQL 3.23.45/Win32 At 12:04 07/12/01 -0800, A. Clausen wrote: Hi, Does print the command show databases the db in question ? and you are able for perform commands on the tables using the mysql client tool ? Regards, Miguel I have been using

Re: Replication Problem on MySQL 3.23.45/Win32

2001-12-10 Thread kadvani
Had a question on Whether or not MySQL Editor supports Db2 Version 5.0. Kumud Advani Sears Canada Inc Architect Council - Corporate Data WareHouse Tel : (416) 510 - 6217 - Before posting, please check:

Re: Replication Problem on MySQL 3.23.45/Win32

2001-12-07 Thread Gustavo A. Baratto
I'm not sure, But I don't think symbolic links are allowed on win2k... Take a look into this... Regards, gustavo On Fri, 2001-12-07 at 12:04, A. Clausen wrote: I have been using replication for several months between to Win2k machines. Last week I upgraded to MySQL 3.23.45, and

Re: Replication Problem on MySQL 3.23.45/Win32

2001-12-07 Thread A. Clausen
] - Original Message - From: Gustavo A. Baratto [EMAIL PROTECTED] To: A. Clausen [EMAIL PROTECTED] Cc: MySQL Mailing List [EMAIL PROTECTED] Sent: Friday, December 07, 2001 12:16 Subject: Re: Replication Problem on MySQL 3.23.45/Win32 I'm not sure, But I don't think symbolic links are allowed

Re: Replication Problem on MySQL 3.23.45/Win32

2001-12-07 Thread Miguel Angel Solórzano
At 12:04 07/12/01 -0800, A. Clausen wrote: Hi, Does print the command show databases the db in question ? and you are able for perform commands on the tables using the mysql client tool ? Regards, Miguel I have been using replication for several months between to Win2k machines. Last week I

Re: Replication problem (with temporary heap tables ?)

2001-10-31 Thread Rafal Jank
= 45219 011031 2:17:41 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log '3306_bin_log.001' at position 71445219 ERROR: 1051 Unknown table 't' 011031 3:09:04 Slave: error running query 'drop table MY_SHOP.t' 011031 3:09:04 Error

Re: replication problem

2001-09-05 Thread Gerald Clark
The slave does not have a server-id. Duc Chau wrote: Hi, this is my first time posting to the list. I've followed mysql replications how-tos to a tee...and I am still not able to get it to work. the master mysql is running on a sun sparc station (SunOS 2.8) with mysql 3.23.41 the file

RE: replication problem

2001-09-05 Thread Duc Chau
To: Duc Chau Cc: [EMAIL PROTECTED] Subject: Re: replication problem The slave does not have a server-id. Duc Chau wrote: Hi, this is my first time posting to the list. I've followed mysql replications how-tos to a tee...and I am still not able to get it to work. the master mysql

Re: replication problem

2001-09-05 Thread Gerald Clark
[mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 05, 2001 7:25 AM To: Duc Chau Cc: [EMAIL PROTECTED] Subject: Re: replication problem The slave does not have a server-id. Duc Chau wrote: Hi, this is my first time posting to the list. I've followed mysql replications how-tos

Re: Replication Problem

2001-09-03 Thread Jeremy Zawodny
On Mon, Sep 03, 2001 at 10:44:57AM +0800, tpchan wrote: Dear all, I managed to set up 1-way master-slave replication using MySQL version 3.23.33. The replication process run fine. However I found out that the master-bin.001 sited on master server log file is growing every day. My

Re: Replication problem

2001-09-03 Thread Jeremy Zawodny
On Thu, Aug 16, 2001 at 08:56:33PM -0700, Lists Servers Email wrote: Does any know how to fix this database replication problem. Last Lines from Err File 010815 21:38:55 Slave thread exiting, replication stopped in log 'salem-bin.013' at position 6867 010815 21:38:55 Error

Re: replication problem

2001-02-12 Thread Gerald L. Clark
Stephen Wong wrote: I try to use the replication feature of the latest stable version 3.23.32. Everyting works find when I follow the instructions until when I tried to stop the slave and then start it. It generated the following messages in the error log: 010212 18:28:08 mysqld

<    1   2