Re: ~Replication errors~

2006-05-12 Thread sheeri kritzer
MySQL's pretty good when it describes an error. (if the error message is vague you might be screwed, but MySQL is pretty good). Which means: 1) You didn't properly change the max_allowed_packet on the master. what does show variables like max_allowed_packet; show you? 2) The slave is

Re: replication errors

2005-03-10 Thread Irek S?onina
Chris Knipe wrote: [..] Sure, there is a syntax error in the query - yes. But why does the master not put the complete query in the bin log? This is the second time in 3 days that it has happened now. Whilst we are on this, how do I tell the slave to skip the query and proceed with

Re: replication errors

2005-03-10 Thread Chris Knipe
Chris Knipe wrote: [..] Sure, there is a syntax error in the query - yes. But why does the master not put the complete query in the bin log? This is the second time in 3 days that it has happened now. Whilst we are on this, how do I tell the slave to skip the query and proceed with

Re: replication errors

2005-03-10 Thread Chris Knipe
Chris Knipe wrote: [..] Sure, there is a syntax error in the query - yes. But why does the master not put the complete query in the bin log? This is the second time in 3 days that it has happened now. Whilst we are on this, how do I tell the slave to skip the query and proceed with

Re: replication errors

2005-03-10 Thread Irek Sonina
Chris Knipe wrote: Now, I've been running for not even 1 hour with the skip-errors enabled A quick check, on ONE table... [EMAIL PROTECTED]:~# mysql --host=mysqldb01 --database=DB -p Enter password: Reading table information for completion of table and column names You can turn off this

Re: replication errors

2005-03-10 Thread Richard Lynch
mysql SELECT COUNT(RadAcctId) FROM RadiusAccounting; +--+ | COUNT(RadAcctId) | +--+ |1144320 | +--+ 1 row in set (1.69 sec) [EMAIL PROTECTED]:~# mysql --host=mysqldb02 --database=DB -p mysql SELECT COUNT(RadAcctId) FROM

Re: replication errors

2005-03-10 Thread Chris Knipe
- Original Message - From: Richard Lynch [EMAIL PROTECTED] To: Chris Knipe [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Friday, March 11, 2005 12:08 AM Subject: Re: replication errors mysql SELECT COUNT(RadAcctId) FROM RadiusAccounting; +--+ | COUNT(RadAcctId

Re: replication errors

2005-03-10 Thread Jeremy Cole
Hi Chris, OK, I can't take this anymore. :) Now, I've been running for not even 1 hour with the skip-errors enabled A quick check, on ONE table... snip So there's already data missing on the slave *shrugs* Yep, you told it to SKIP ERRORS. That means that if any query generates an error,

Re: replication errors

2005-03-10 Thread Chris Knipe
So there's already data missing on the slave *shrugs* Yep, you told it to SKIP ERRORS. That means that if any query generates an error, for any reason, it's just going to skip over it and move on. So data was missing on your slave the moment you restarted replication -- it skipped the

Re: replication errors

2005-03-10 Thread Keith Ivey
Irek Sonina wrote: I was thinking that master is executing the same queries that slave does - if an error exists on slave then it first comes up on the master and master is not executing it either. You prove that I was wrong... now I must check the integrity of the data on my slaves, which all

RE: Replication errors...

2004-03-25 Thread Stanton, Brian
Thanks! I was hoping it was something that had already been found. I'll upgrade as soon as I can. Thanks, Brian -Original Message- From: Sasha Pachev [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 10:47 PM To: Stanton, Brian Cc: '[EMAIL PROTECTED]' Subject: Re: Replication

Re: Replication errors...

2004-03-24 Thread Sasha Pachev
Stanton, Brian wrote: Shortly after the MySQL 4.0 line went to production, I upgraded to mysql 4.0.12. Since then my slave has been getting corrupted tables 2 to 3 times every month. I've also seen this problem in mysql 4.0.13. When I run a check table on the table in question it gives the

Re: Replication Errors *NEWEST*

2002-11-24 Thread Lewis Watson
NEWEST** I am now getting this error while trying to Replicate to a second MySQL server. 021125 0:41:01 Slave: Failed reading log event, reconnecting to retry, log 'bsd1-bin.001' position 73 021125 0:41:01 Slave: reconnected to master '[EMAIL

Re: Replication Errors

2002-11-18 Thread Jeremy Zawodny
On Mon, Nov 18, 2002 at 11:47:48AM -0500, Michael T. Babcock wrote: Any suggestions? This is a live DB ... 021118 10:43:47 InnoDB: Started /usr/libexec/mysqld: ready for connections 1254 021118 10:43:49 Slave: connected to master '[EMAIL PROTECTED]:3303', replication started in log

Re: Replication Errors

2002-11-18 Thread Michael T. Babcock
Jeremy Zawodny wrote: I hate to ask this, bug did you change anything? :-) In the data? Heck ya :-) ... the versions of the software? No -- although either of them has restarted / flushed logs from time to time as necessary (I don't have a log rotation program yet for the binary logs

Re: Replication errors

2002-07-03 Thread Dicky Wahyu Purnomo
Pada Wed, 3 Jul 2002 12:56:30 -0700 Jeff Kilbride [EMAIL PROTECTED] menulis : Is this just a normal timeout error, because there's currently very little activity on these machines? Or is there some other problem? The slave_net_timeout value is at it's default of 3600, so I would expect to