- Original Message -
> From: "Néstor"
>
> 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 without knowing
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 parall
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 wrote:
> HI Igor,
>
> Are you saying to add these lines to the my.cnf file:
> replicate-
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 ei
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, ref
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,
Ig
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:
http://crazytoon.com/2008/01/29/mysql-how-do-you-set-u
2012/11/30 Néstor
> I am trying to set up mysql replication on 2 systems but Once I get it
> going, I get the following an error 1062,
>
>
> 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 have repeated th
- Original Message -
> From: "divesh kamra"
>
> 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 it
further. "It e
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 wrote:
>
>
> Am 30.11.2012 23:52, schrieb Rick James:
> > Possible causes:
> > * Someone is writing to the Slave
>
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 clo
CREATE TABLE (for a table that is in trouble)
> -Original Message-
> From: Néstor [mailto:rot...@gmail.com]
> Sent: Friday, November 30, 2012 1:24 PM
> To: mysql@lists.mysql.com
> Subject: MySQL Replication Error
>
> I am trying to set up mysql replication on 2 syst
I am trying to set up mysql replication on 2 systems but Once I get it
going, I get the following an error 1062,
which is a duplicate entry and my 'slave status' shows:
Slave_IO_Running: Yes
Slave_SQL_Running: No
And this is the error on my mysql.err file:
121130 12:41:53 [Note
ter and the slave?
> Was a snapshot of the master placed on the slave
> before beginning
> replication?
> I hate to ask such simple questions but I am just
> checking.
>
> Victor
>
> -Original Message-
> From: Natale Babbo
> To: [EMAIL PROTECTED]
> Sent
i get the following error in the connection
slave->master while setting up a replication between
two MySQLServer(slave and master both windows XP):
.err file on slave:
MySql: ready for connections
021023 14:08:34 InnoDB: Started
021023 14:08:35 Slave I/O thread: connected to master
'[EMAIL PROTE
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:
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 Error reading packet from server: Binary log is not open
(read_errno 0,server_errno=2000)
up to do
So in skipping 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 replic
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
>
>
>
&g
21, 2002 5:18 PM
To: Luc Foisy
Cc: [EMAIL PROTECTED]
Subject: Re: MySQL replication error
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 lo
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, 21
Would anyone be able to tell me why this happened, and how I could fix it?
mysql> show slave status\G
*** 1. row ***
Master_Host: 209.217.92.34
Master_User: repslave2
Master_Port: 3306
Connect_retry: 60
Log_F
22 matches
Mail list logo
