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 wrote:
>
2 fax 636-755-2502
> dirk.bre...@nisc.coop www.nisc.coop
>
> -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,
isc.coop
-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
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 mas
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 wrote:
> Could not find
> first log file name in binary log index file
--
MySQL General Ma
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 d
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 98
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:
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 f
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 mysq
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 tests
I left out the details because of the fear of putting
people to sleep. Here it goes
The requirement is to design High Availability for an
Application that is using a MySQL database. The
following is the configuration I have in mind.
CONFIGURATION:
- Two machines, Primary and Secondary. Each
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 mirro
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 n
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 re
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 I
> 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 dupl
Hi,
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 duplic
At 07:13 PM 1/23/01 -0800, Jeremy D. Zawodny wrote:
>What sort of errors? Can you give an example?
Sure, like a record already existing - it attempts an insert into a unique
field that is there, and turns off replication.
>Are you sure your binary log was in sync with the slave's copy of the
>da
On Tue, Jan 23, 2001 at 04:01:00PM -0500, Jeremy Wilson wrote:
> 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 sort
20 matches
Mail list logo
