Withers [mailto:joh...@pixelated.net]
Sent: Thursday, March 26, 2009 18:00
To: mysql@lists.mysql.com
Subject: Re: Replication Issues
I notice in the startup messages there is an underscore in the file
names, but there are dashes in the dir list you provided. ???
On 3/26/09, Dirk Bremer dirk.bre
We recently completed a project where all of our production servers were
replaced. As part of this project, one of the new servers acted as a
replication-slave to one of the old servers, which was the
replication-master. I had replication up and running just fine on
multiple slaves for a couple of
Most likely something is wrong in your AMSCD2-relay-bin.index file.
Check this out:
http://forums.mysql.com/read.php?26,9390,242387#msg-242387
Walter Heck
On Thu, Mar 26, 2009 at 10:02 PM, Dirk Bremer dirk.bre...@nisc.coop wrote:
Could not find
first log file name in binary log index file
Hi Dirk,
it seems that the information about binary files on the master contained
in the mysql-bin.index does not match the actual files on the disk.
The first two log messages are just info on the slave starting the two
replication threads,
the other two seem to be a message coming from the
-Original Message-
From: Claudio Nanni [mailto:claudio.na...@gmail.com]
Sent: Thursday, March 26, 2009 16:18
To: Dirk Bremer
Cc: mysql@lists.mysql.com
Subject: Re: Replication Issues
Hi Dirk,
it seems that the information about binary files on the master contained
in the mysql-bin.index does
, March 26, 2009 16:18
To: Dirk Bremer
Cc: mysql@lists.mysql.com
Subject: Re: Replication Issues
Hi Dirk,
it seems that the information about binary files on the master contained
in the mysql-bin.index does not match the actual files on the disk.
The first two log messages are just info
Hi All,
innodb_file_per_table will create individual .ibd file for each table. If
mysql master has single ibdata file and mysql slave (used
'innodb_file_per_table') has multiple .ibd files. Is there any other issues
by having replication in this way.
Thanks
--
Krishna Chandra Prajapati
MySQL
I posted this message on the Replication list, but have got no responses,
so, I figured I'd try here.
I just set up Replication recently with a Web Server 2003 server being the
master and a Windows 2000 server machine being the slave. When I got done, I
did a few tests, and all appeared to be
Hi Jesse,
Jesse wrote:
I posted this message on the Replication list, but have got no
responses, so, I figured I'd try here.
I just set up Replication recently with a Web Server 2003 server being the
master and a Windows 2000 server machine being the slave. When I got
done, I
did a few
I can't think of anything other than looking deeper into the MySQL log
files. I'm not sure where those are on Windows, but I imagine it's not
all going to the event log. Maybe there is something in c:\program
files\mysql 5\ (or wherever you installed MySQL). Try looking for a file
named
Jesse wrote:
I can't think of anything other than looking deeper into the MySQL log
files. I'm not sure where those are on Windows, but I imagine it's
not all going to the event log. Maybe there is something in
c:\program files\mysql 5\ (or wherever you installed MySQL). Try
looking for a
What is the event at that position in the binlog? Use the mysqlbinlog
tool to see, or on the master you can run SHOW BINLOG EVENTS (check the
manual for the full syntax).
If I'm reading this right (and I'm probably not), the log goes from position
98 to position 557 Position 98 has a DELETE
Jesse wrote:
What is the event at that position in the binlog? Use the mysqlbinlog
tool to see, or on the master you can run SHOW BINLOG EVENTS (check
the manual for the full syntax).
If I'm reading this right (and I'm probably not), the log goes from
position 98 to position 557 Position
Hopefully that's enough info for you to decide whether you read it right.
But it looks like your slave had some issue with that. Do you have a lot
of privileges? One of the Google engineers told me he's sometimes seen
FLUSH PRIVILEGES break replication with a lot of privileges.
Whoever was
this
you can start your mysql with skip-slave-error=1062 in such case these
duplicates will not repeat.
Thanks Regards
Dilipkumar
- Original Message -
From: David Hillman [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Wednesday, July 26, 2006 12:34 AM
Subject: Re: Slave Replication
Hi, we have been losing slaves due to errors in replication. See error
message below. Would appreciate if anyone could share if they have seen same
issues. It seems something may be getting corrupted in the binary log.
Thanks.
The error reads:
Last_error: Error 'Duplicate entry '12312942'
On Jul 25, 2006, at 12:47 PM, David Nance wrote:
Hi, we have been losing slaves due to errors in replication. See error
message below. Would appreciate if anyone could share if they have
seen same
issues. It seems something may be getting corrupted in the binary log.
Thanks.
The error reads:
On Wed, Feb 18, 2004 at 02:18:59PM -0800, Gowtham Jayaram wrote:
Hello all:
I am looking into the Replication issues that surface in a Failover
scenario (Master goes down and Slave is pressed into service).
I understand that it is critical for the Master and Slave databases
to mirror each
; when machine fails, the other
machine is brought online against the same data.
All feedback is most welcome.
Gowtham.
--- Jeremy Zawodny [EMAIL PROTECTED] wrote:
On Wed, Feb 18, 2004 at 02:18:59PM -0800, Gowtham
Jayaram wrote:
Hello all:
I am looking into the Replication issues
Hello all:
I am looking into the Replication issues that surface
in a Failover scenario (Master goes down and Slave is
pressed into service).
I understand that it is critical for the Master and
Slave databases to mirror each other for Replication
to work. I am trying to ensure
I have a setup of 3 servers, with MySQL replication in a round-robin fashion
between all 3. So far, any writes to a particular table are done only on one
machine at any time. The replication is used as a hot backup, not a
load-balancing thing.
I now have an instance where I'd like to do
On Wed, Feb 12, 2003 at 10:59:00AM +0800, Trevor Phillips wrote:
I have a setup of 3 servers, with MySQL replication in a round-robin fashion
between all 3. So far, any writes to a particular table are done only on one
machine at any time. The replication is used as a hot backup, not a
Hey guys,
I followed the mysql replication instructions in the mysql manual to the
tee. http://www.mysql.com/doc/en/Replication_HOWTO.html However replication
immediately fails. I tailed the logs and noticed that it failed on an
insert query on key1, claiming duplicate entry. Now I've read
Dan wrote:
not attempting to write to the index field. I also attempted to have it skip
the entry with the SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; command. This
command failed. It did not fail when I eliminated the GLOBAL word in the
command like so: SET SQL_SLAVE_SKIP_COUNTER=1; However, still
I have a few questions about Replication. I've already read the basic
replication page here:
http://www.mysql.com/doc/en/Replication_HOWTO.html
I am running MySQL-MAX 3.23.53 for Linux on my master server, and the
same version on Windows 2000 for the slave.
#1 - Can I replicate from Linux to
, November 18, 2002 2:45 PM
Subject: Newbie Replication Issues
I have a few questions about Replication. I've already read the basic
replication page here:
http://www.mysql.com/doc/en/Replication_HOWTO.html
I am running MySQL-MAX 3.23.53 for Linux on my master server, and the
same version
At 15:45 -0500 11/18/02, Rick Root wrote:
I have a few questions about Replication. I've already read the
basic replication page here:
http://www.mysql.com/doc/en/Replication_HOWTO.html
I am running MySQL-MAX 3.23.53 for Linux on my master server, and
the same version on Windows 2000 for the
Hello List,
I'm using MySQL 4.0.3-beta on 2 RedHat 7.3 Boxes belonging to a 2 node HA
Cluster.
To allow the takeover of the database node I formed a replication ring.
So node1 replicates to node2 and the other way round.
Read/Write operations are only done on Node 2.
The nodes are connected
Below is the output from the error log
I started slave replication, it replicated about 5 tables, then just after
it created the next table, it stops. I am not sure of the problem (does
anyone know what server_errno 2013 is?)
020513 10:01:07 Error reading packet from server: Lost connection
Luc,
Luc Foisy wrote:
MySQL version 3.23.32
(please don't ask me to upgrade to the newest version of mysql as an answer)
I'm very sorry but an upgrade seems to be necessary:
if I recall this correctly we had to upgrade to 3.23.33 a year ago or so
because the changelog pointed towards a
MySQL version 3.23.32
(please don't ask me to upgrade to the newest version of mysql as an answer)
Everytime the replication server gets reset, the slave properties gets all
messed up
I am assuming the master.info gets trashed
Is this a known issue for this version?
Anyways, I can use the
Humph. Undocumented CHANGE MASTER TO MASTER_CONNECT_RETRY=60;
Still asking the other question if there is a fix for the problem or not...
-Original Message-
From: Luc Foisy [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 03, 2002 11:37 AM
To: MYSQL-List (E-mail)
Subject: Replication
On Saturday 12 January 2002 20:53, Jeremy Zawodny wrote:
On Fri, Jan 11, 2002 at 08:08:51AM -0800, Kyle Hayes wrote:
We write our own replication system using our own checkpointing and
code. We start with the update logs (we're not happy about the
future removal of the update logs because
Hi!
Two-way replication is complex, and even more difficult is coping with
broken communications.
MySQL only supports one-way replication (master - slaves). Auto-inc column
values are communicated in the binlog to the slaves.
Some ideas:
- Generate primary keys where you concatenate the id of
On Fri, Jan 11, 2002 at 08:08:51AM -0800, Kyle Hayes wrote:
We write our own replication system using our own checkpointing and
code. We start with the update logs (we're not happy about the
future removal of the update logs because of this). I've looked
through the MySQL source to see if
On Thursday 10 January 2002 17:22, Matthew Walker wrote:
Where I work, we're at the point of needing to maintain two database
servers, one inhouse, and the other at another physical location. We
need to replicate between the servers, to keep them both up to date, as
both will be getting
Jeremy Wilson:
I tested replication recently and found it extremely lacking. Even the
most minor of errors causes the daemon to stop replicating, effectively
rendering the ability useless to me, as I use mysql for authentication.
What errors are you talking about? Errors like duplicate
I tested replication recently and found it extremely lacking. Even the
most minor of errors causes the daemon to stop replicating, effectively
rendering the ability useless to me, as I use mysql for authentication.
Is there some configuration command to make it *ignore* errors and continue
to
38 matches
Mail list logo
