- Original Message -
From: Néstor rot...@gmail.com
I spoke to soon!!!
Here is the error about 1.5 hours after replication has started.
121205 16:39:51 [ERROR] Slave: Error 'Duplicate entry '3468897'
for
Yes, that's what you get for running SQL_SLAVE_SKIP_COUNTER
Yes that's correct.
it needs to be added on the slave side under [mysqld] section usually
close to the place where you define your replication settings (for
convenience only).
The reason why server failed to start difficult to guess without error log.
this will prevent all tables under
Hi Néstor,
You might want to put those lines into your my.cnf under replication
section and restart the slave:
replicate-wild-ignore-table=dbname%.watchdog%
and may be this as well:
replicate-wild-ignore-table=dbname%.cache%
Do you really need to replicate cache and session tables?
Cheers,
I spoke to soon!!!
Here is the error about 1.5 hours after replication has started.
121205 16:39:51 [ERROR] Slave: Error 'Duplicate entry '3468897' for
key 1' on query. Default database: 'parallax'. Query: 'INSERT INTO watchdog
(uid, type, message, variables, severity, link, location,
In regards to the second part of your email.
You don't have errors in your mysql.err log. Those are notes saying that
you started IO and SQL replication threads after you skipped an
replication error and run start slave command.
I wouldn't run SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; command
I added those line to the slave's my.cnf and mysql would not start
replicate-wild-ignore-table=parallax%.watchdog%
replicate-wild-ignore-table=parallax%.cache%
Nestor
On Thu, Dec 6, 2012 at 4:39 PM, Néstor rot...@gmail.com wrote:
HI Igor,
Are you saying to add these lines to the my.cnf
- Original Message -
From: divesh kamra kamra.div...@gmail.com
slave-skip-errors=1062 --- in my.cnf and restart mysql
Really? Just like that? Without even knowing what it does or what the problem
is?
If you have replication errors, this kind of stuff is only going to break
2012/11/30 Néstor rot...@gmail.com
I am trying to set up mysql replication on 2 systems but Once I get it
going, I get the following an error 1062,
skip
I have re-installed the database on the slave also to see if this fixes the
problem
but after a few minutes I get the same error. I
I was about to reply with a long message of all the steps I followed to
create replication but I did my steps about an hour ago and I have not
seen the replication fail so far.
BTW, I created my replication following the info on this web page:
Hi
first check this thought application end
or
There is another way
slave-skip-errors=1062 --- in my.cnf and restart mysql
On Sat, Dec 1, 2012 at 4:30 AM, Reindl Harald h.rei...@thelounge.netwrote:
Am 30.11.2012 23:52, schrieb Rick James:
Possible causes:
* Someone is writing
Possible causes:
* Someone is writing to the Slave.
* The Slave was not in synch with the Master.
* Schemas are different between Master and Slave.
* Someone is changing the POS for replication.
After you have eliminated those possibilities, provide
SHOW SLAVE STATUS \G
SHOW MASTER STATUS;
SHOW
Am 30.11.2012 23:52, schrieb Rick James:
Possible causes:
* Someone is writing to the Slave
that is why the option read-only exists for my.cnf
* The Slave was not in synch with the Master.
* Schemas are different between Master and Slave
should not happen if the slave is properly cloned
No ... I'm just setting up the replication for the
first time.
I make a dump of the master and i replaced it on the
slave.
thanks and bye.
--- Victor Pendleton [EMAIL PROTECTED] ha
scritto: Has the replication worked previously for
you?
If so, have you reset the master and the slave?
Looks like you don't have binary logging turned on on the master.
louie miranda wrote:
021009 12:56:49 mysqld started
/usr/sbin/mysqld: ready for connections
021009 12:56:49 Slave: connected to master '[EMAIL PROTECTED]:3306',
replication started in log 'FIRST' at position 4
021009 12:56:49
1' on query
'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())'
Skip_counter: 0
1 row in set (0.00 sec)
-Original Message-
From: chad kellerman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 5:18 PM
To: Luc Foisy
Cc: [EMAIL PROTECTED]
Subject: Re: MySQL replication
(CreateStamp) VALUES (NOW())'
Skip_counter: 0
1 row in set (0.00 sec)
-Original Message-
From: chad kellerman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 5:18 PM
To: Luc Foisy
Cc: [EMAIL PROTECTED]
Subject: Re: MySQL replication error
Luc,
I new
these transactions, am I losing data?
-Original Message-
From: chad kellerman [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 22, 2002 11:57 AM
To: Luc Foisy
Cc: [EMAIL PROTECTED]
Subject: Re: MySQL replication error
Luc,
The problem is that in the replication somewhere an update
Luc,
I new to this mailinglist ( this is my first posting) But I have worked a little
with replication.
Try if the replicator is still down.
set sql_slave_skip_counter = 1; slave start
on the slave as long as you are sure the master is ok.
Let me know is this worked.
-chad
On Thu,
18 matches
Mail list logo
