bruce wrote:
hi..
doing a simple test of master/slave replication, using mysql.
i have two test systems:
master - foo (192.168.10.13)
slave - cat (192.168.20.20)
on both machines, i created a testmasterdb. on the master, i populated the
tbl within the db with some test data. there are no
hi..
doing a simple test of master/slave replication, using mysql.
i have two test systems:
master - foo (192.168.10.13)
slave - cat (192.168.20.20)
on both machines, i created a testmasterdb. on the master, i populated the
tbl within the db with some test data. there are no tbls in the sla
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 actu
Hi,
Iam getting the following error on my Mysql Slave server. This happened
when my disk space got full and there was no space left on the device. I
managed to free up some space and then ran
mysql> STOP SLAVE
mysql> CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000110',
MASTER_LOG_POS=850202232;
Irek Słonina 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 a
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 UPDATE
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...
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 a
- Original Message -
From: "Richard Lynch" <[EMAIL PROTECTED]>
To: "Chris Knipe" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, March 11, 2005 12:08 AM
Subject: Re: replication errors
mysql> SELECT COUNT(RadAcctId) FROM RadiusAccounting;
+--
> 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) FR
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 featu
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 th
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 th
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 th
Lo again,
Master and Slave server, both running 5.0.2-LOG (Exactly the same versions).
On the master, everything is working fine. Data that gets inserted /
updated / deleted etc goes into the bin log, and gets replicated to the
slave.
HOWEVER
On the slave, I am getting syntax errors from the qu
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:
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 follo
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 following results:
+-
Hi
I've got a master and a slave both at 3.23.49. I've been running
replication for the last 3 months and all of a sudden I've got queries
failing on the slave with duplicate entries (error 1062). From the
documentation all I can figure out is that there's a possibility I might be
using differen
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 PROTECTED]:3306',replicatio
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 mind
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 lo
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 'FIRST' at
position 31804350 ' at line 1
ERR
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 expe
I have replication running successfully between two Linux boxes running
3.23.51. However, I'm getting the following error very frequently (every
30 - 60 seconds) in my slave error log:
-
020703 15:41:09 Error reading packet from server: (server_errno=1159)
020703 15:42:0
Anyone have any ideas as to how I should handle a case
of the following error?
020102 13:27:28 Slave: Failed reading log event, reconnecting to retry, log
'db1-bin.008' position 1064155638
020102 13:27:28 Slave: connected to master '[EMAIL PROTECTED]:3306',replication
resumed in log 'db1-bin
tentional I would appreciate knowing, so I can determine what needs
redesigned in my system.
>Submitter-Id:
>Originator: wrath
>Organization:
>MySQL support: none
>Synopsis: Replication errors with INSERT INTO..SELECT FROM
>Severity: serious
>Priority: med
I have a one-way replication setup where the master is out of state, and the
slave is local. The connection between the machines is high-speed, but not
100% reliable. Every once in a while, my slave thread stops because of a
duplicate key entry. I'm puzzled by this for several reasons:
1. Insertio
27 matches
Mail list logo
