Re: MySQL Replication Error

[Johan De Meersman]

- 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 
what the problem is.

Your database is now nicely out of sync, and hopefully it's just the watchdog.

The *proper* way of resolving this is to resync the entire database. You *may* 
get away with deleting watchdog entry 3468897 and restarting replication as 
someone has suggested, but I suspect you'll find another half-million of them.

Look at the Percona Toolkit, specifically mk-table-checksum and mk-table-sync, 
understand how they work and then apply them. If there's too many differences 
by now, your only recourse will be to completely reprovision the slave, though.

-- 
Linux Bier Wanderung 2012, now also available in Belgium!
August, 12 to 19, Diksmuide, Belgium - http://lbw2012.tuxera.be

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

Re: MySQL Replication Error

[Igor Shevtsov]

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 parallax db with watchdog bit in the 
name to be replicated.


another option
*|replicate-ignore-table=/|parallax.watchdog|/| 
* 



and restart server








On 07/12/12 00:56, Néstor wrote:

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-wild-ignore-table=dbname%.watchdog%
replicate-wild-ignore-table=dbname%.cache%

Correct?

Thanks,

Nestor :-)



On Thu, Dec 6, 2012 at 3:07 PM, Igor Shevtsov wrote:


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 either as
it makes your tables inconsistent.
I'd rather deleted offending row on the slave and started replication. In
this case insert would've succeed and tables would become consistent again.






On 06/12/12 21:59, Néstor wrote:


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, referer,
hostname, timestamp)
  VALUES
  (0, 'page not found', 'images/internet_explorer/**
borderTopLeft.png',
'N;', 4, '','
http://www.sdcwa.org/es/**images/internet_explorer/**borderTopLeft.png',
'',
'10.20.141.24', 1354754352)', Error_code: 1062
121205 16:39:51 [ERROR] Error running query, slave SQL thread aborted.
Fix
the problem, and restart the slave SQL thread with "SLAVE START". We
stopped at log 'mysql-bin.000289' position 86451409

--**--
Sorry for the long message, below are the steps use to create my
replication.


When I created the replication, I followed the steps here :
http://crazytoon.com/2008/01/**29/mysql-how-do-you-set-up-**
masterslave-replication-in-**mysql-centos-rhel-fedora/
   I am on a red hat server.
---
I set my firewall to accept info from server1 on server2
SERVER1:
tcp0  0 wahoo.sdcwa.org:mysql   wahooesc.sdcwa.org:52131
   ESTABLISHED 30145/mysqld
SERVER2:
tcp0  0 wahooesc.sdcwa.org:52131www.sdcwa.org:mysql
ESTABLISHED 30875/mysqld
-

I have try using the SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;

I have also done these steps where in SERVER1
FLUSH TABLES WITH READ LOCK;
SHOW MASTER STATUS;
+--+--**+--+--**+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+--+--**+--+--**+
| mysql-bin.000289 | 42394063 |  |  |
+--+--**+--+--**+

Then Dump SERVER1 database then you unlock SERVER1 database
and copy it to SERVER2 then FLUSH TABLES WITH READ LOCK;

I proceed to STOP SLAVE then add the database to SERVER2 then
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.**000289',
MASTER_LOG_POS=42394063; to synch with the SERVER1
Then I start SERVER2 and the output of  slave status is:

mysql> SHOW SLAVE STATUS\G
*** 1. row ***
   Slave_IO_State: Waiting for master to send event
  Master_Host: 10.168.1.21
  Master_User: sdcwa_slave
  Master_Port: 3306
Connect_Retry: 60
  Master_Log_File: mysql-bin.000289
  Read_Master_Log_Pos: 55848766
   Relay_Log_File: mysql-relay-bin.02
Relay_Log_Pos: 13454938
Relay_Master_Log_File: mysql-bin.000289
 Slave_IO_Running: Yes
Slave_SQL_Running: Yes
  Replicate_Do_DB:
  Replicate_Ignore_DB:
   Replicate_Do_Table:
   Replicate_Ignore_Table:
  Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
   Last_Errno: 0
   Last_Error:
 Skip_Counter: 0
  Exec_Master_Log_Pos: 55848766
  Relay_Log_Space: 13454938
  Until_Condition: None
   

Re: MySQL Replication Error

[Néstor]

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-wild-ignore-table=dbname%.watchdog%
> replicate-wild-ignore-table=dbname%.cache%
>
> Correct?
>
> Thanks,
>
> Nestor :-)
>
>
>
> On Thu, Dec 6, 2012 at 3:07 PM, Igor Shevtsov wrote:
>
>> 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 either as
>> it makes your tables inconsistent.
>> I'd rather deleted offending row on the slave and started replication. In
>> this case insert would've succeed and tables would become consistent again.
>>
>>
>>
>>
>>
>>
>> On 06/12/12 21:59, Néstor wrote:
>>
>>> 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, referer,
>>> hostname, timestamp)
>>>  VALUES
>>>  (0, 'page not found', 'images/internet_explorer/**
>>> borderTopLeft.png',
>>> 'N;', 4, '','
>>> http://www.sdcwa.org/es/**images/internet_explorer/**borderTopLeft.png',
>>> '',
>>> '10.20.141.24', 1354754352)', Error_code: 1062
>>> 121205 16:39:51 [ERROR] Error running query, slave SQL thread aborted.
>>> Fix
>>> the problem, and restart the slave SQL thread with "SLAVE START". We
>>> stopped at log 'mysql-bin.000289' position 86451409
>>>
>>> --**--
>>> Sorry for the long message, below are the steps use to create my
>>> replication.
>>>
>>>
>>> When I created the replication, I followed the steps here :
>>> http://crazytoon.com/2008/01/**29/mysql-how-do-you-set-up-**
>>> masterslave-replication-in-**mysql-centos-rhel-fedora/
>>>   I am on a red hat server.
>>> ---
>>> I set my firewall to accept info from server1 on server2
>>> SERVER1:
>>> tcp0  0 wahoo.sdcwa.org:mysql   wahooesc.sdcwa.org:52131
>>>   ESTABLISHED 30145/mysqld
>>> SERVER2:
>>> tcp0  0 wahooesc.sdcwa.org:52131www.sdcwa.org:mysql
>>> ESTABLISHED 30875/mysqld
>>> -
>>>
>>> I have try using the SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;
>>>
>>> I have also done these steps where in SERVER1
>>> FLUSH TABLES WITH READ LOCK;
>>> SHOW MASTER STATUS;
>>> +--+--**+--+--**+
>>> | File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
>>> +--+--**+--+--**+
>>> | mysql-bin.000289 | 42394063 |  |  |
>>> +--+--**+--+--**+
>>>
>>> Then Dump SERVER1 database then you unlock SERVER1 database
>>> and copy it to SERVER2 then FLUSH TABLES WITH READ LOCK;
>>>
>>> I proceed to STOP SLAVE then add the database to SERVER2 then
>>> CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.**000289',
>>> MASTER_LOG_POS=42394063; to synch with the SERVER1
>>> Then I start SERVER2 and the output of  slave status is:
>>>
>>> mysql> SHOW SLAVE STATUS\G
>>> *** 1. row ***
>>>   Slave_IO_State: Waiting for master to send event
>>>  Master_Host: 10.168.1.21
>>>  Master_User: sdcwa_slave
>>>  Master_Port: 3306
>>>Connect_Retry: 60
>>>  Master_Log_File: mysql-bin.000289
>>>  Read_Master_Log_Pos: 55848766
>>>   Relay_Log_File: mysql-relay-bin.02
>>>Relay_Log_Pos: 13454938
>>>Relay_Master_Log_File: mysql-bin.000289
>>> Slave_IO_Running: Yes
>>>Slave_SQL_Running: Yes
>>>  Replicate_Do_DB:
>>>  Replicate_Ignore_DB:
>>>   Replicate_Do_Table:
>>>   Replicate_Ignore_Table:
>>>  Replicate_Wild_Do_Table:
>>> Replicate_Wild_Ignore_Table:
>>>   Last_Errno: 0
>>>   Last_Error:
>>> Skip_Counter: 0
>>>  Exec_Master_Log_Pos: 55848766
>>>  Relay_Log_Space: 13454938
>>>  Until_Condition: None
>>>   Until_Log_File:
>>>Until_Log_Pos: 0
>>>   Master_SSL_Allowed: No
>>>   Master_SSL_CA_File:
>>>   Master_SSL_CA_Path:
>>>  Master_SSL_Cert:
>>>Master_SSL_Ciph

Re: MySQL Replication Error

[Igor Shevtsov]

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 either as 
it makes your tables inconsistent.
I'd rather deleted offending row on the slave and started replication. 
In this case insert would've succeed and tables would become consistent 
again.






On 06/12/12 21:59, Néstor wrote:

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, referer,
hostname, timestamp)
 VALUES
 (0, 'page not found', 'images/internet_explorer/borderTopLeft.png',
'N;', 4, '','
http://www.sdcwa.org/es/images/internet_explorer/borderTopLeft.png', '',
'10.20.141.24', 1354754352)', Error_code: 1062
121205 16:39:51 [ERROR] Error running query, slave SQL thread aborted. Fix
the problem, and restart the slave SQL thread with "SLAVE START". We
stopped at log 'mysql-bin.000289' position 86451409


Sorry for the long message, below are the steps use to create my
replication.


When I created the replication, I followed the steps here :
http://crazytoon.com/2008/01/29/mysql-how-do-you-set-up-masterslave-replication-in-mysql-centos-rhel-fedora/
  I am on a red hat server.
---
I set my firewall to accept info from server1 on server2
SERVER1:
tcp0  0 wahoo.sdcwa.org:mysql   wahooesc.sdcwa.org:52131
  ESTABLISHED 30145/mysqld
SERVER2:
tcp0  0 wahooesc.sdcwa.org:52131www.sdcwa.org:mysql
ESTABLISHED 30875/mysqld
-

I have try using the SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;

I have also done these steps where in SERVER1
FLUSH TABLES WITH READ LOCK;
SHOW MASTER STATUS;
+--+--+--+--+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+--+--+--+--+
| mysql-bin.000289 | 42394063 |  |  |
+--+--+--+--+

Then Dump SERVER1 database then you unlock SERVER1 database
and copy it to SERVER2 then FLUSH TABLES WITH READ LOCK;

I proceed to STOP SLAVE then add the database to SERVER2 then
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000289',
MASTER_LOG_POS=42394063; to synch with the SERVER1
Then I start SERVER2 and the output of  slave status is:

mysql> SHOW SLAVE STATUS\G
*** 1. row ***
  Slave_IO_State: Waiting for master to send event
 Master_Host: 10.168.1.21
 Master_User: sdcwa_slave
 Master_Port: 3306
   Connect_Retry: 60
 Master_Log_File: mysql-bin.000289
 Read_Master_Log_Pos: 55848766
  Relay_Log_File: mysql-relay-bin.02
   Relay_Log_Pos: 13454938
   Relay_Master_Log_File: mysql-bin.000289
Slave_IO_Running: Yes
   Slave_SQL_Running: Yes
 Replicate_Do_DB:
 Replicate_Ignore_DB:
  Replicate_Do_Table:
  Replicate_Ignore_Table:
 Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
  Last_Errno: 0
  Last_Error:
Skip_Counter: 0
 Exec_Master_Log_Pos: 55848766
 Relay_Log_Space: 13454938
 Until_Condition: None
  Until_Log_File:
   Until_Log_Pos: 0
  Master_SSL_Allowed: No
  Master_SSL_CA_File:
  Master_SSL_CA_Path:
 Master_SSL_Cert:
   Master_SSL_Cipher:
  Master_SSL_Key:
   Seconds_Behind_Master: 0
1 row in set (0.00 sec)
---

I get the folllowing on my mysql.err:
121205 15:09:56 [Note] Slave SQL thread initialized, starting replication
in log 'mysql-bin.000289' at position 42394063, relay log
'/var/log/mysql/mysql-relay-bin.01' position: 4
121205 15:09:56 [Note] Slave I/O thread: connected to master '
sdcwa_slave@192.168.1.21:3306',  replication started in log
'mysql-bin.000289' at position 42394063


Everything is GOOD, for a little while and then I get an error on mysql.err:

-

Now if I do the SKIP FLAG many times, I will error after error...
I do not see how replication works so well for others if I am using the
steps in the link
on top of this message.

THANKS!!!


On Wed, Dec 5, 2012 at 3:42 AM, Manuel Arostegui  wrote:



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

Re: MySQL Replication Error

[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
key 1' on query. Default database: 'parallax'. Query: 'INSERT INTO watchdog
(uid, type, message, variables, severity, link, location, referer,
hostname, timestamp)
VALUES
(0, 'page not found', 'images/internet_explorer/borderTopLeft.png',
'N;', 4, '', '
http://www.sdcwa.org/es/images/internet_explorer/borderTopLeft.png', '',
'10.20.141.24', 1354754352)', Error_code: 1062
121205 16:39:51 [ERROR] Error running query, slave SQL thread aborted. Fix
the problem, and restart the slave SQL thread with "SLAVE START". We
stopped at log 'mysql-bin.000289' position 86451409


Sorry for the long message, below are the steps use to create my
replication.


When I created the replication, I followed the steps here :
http://crazytoon.com/2008/01/29/mysql-how-do-you-set-up-masterslave-replication-in-mysql-centos-rhel-fedora/
 I am on a red hat server.
---
I set my firewall to accept info from server1 on server2
SERVER1:
tcp0  0 wahoo.sdcwa.org:mysql   wahooesc.sdcwa.org:52131
 ESTABLISHED 30145/mysqld
SERVER2:
tcp0  0 wahooesc.sdcwa.org:52131www.sdcwa.org:mysql
ESTABLISHED 30875/mysqld
-

I have try using the SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;

I have also done these steps where in SERVER1
FLUSH TABLES WITH READ LOCK;
SHOW MASTER STATUS;
+--+--+--+--+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+--+--+--+--+
| mysql-bin.000289 | 42394063 |  |  |
+--+--+--+--+

Then Dump SERVER1 database then you unlock SERVER1 database
and copy it to SERVER2 then FLUSH TABLES WITH READ LOCK;

I proceed to STOP SLAVE then add the database to SERVER2 then
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000289',
MASTER_LOG_POS=42394063; to synch with the SERVER1
Then I start SERVER2 and the output of  slave status is:

mysql> SHOW SLAVE STATUS\G
*** 1. row ***
 Slave_IO_State: Waiting for master to send event
Master_Host: 10.168.1.21
Master_User: sdcwa_slave
Master_Port: 3306
  Connect_Retry: 60
Master_Log_File: mysql-bin.000289
Read_Master_Log_Pos: 55848766
 Relay_Log_File: mysql-relay-bin.02
  Relay_Log_Pos: 13454938
  Relay_Master_Log_File: mysql-bin.000289
   Slave_IO_Running: Yes
  Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
 Replicate_Do_Table:
 Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
 Last_Errno: 0
 Last_Error:
   Skip_Counter: 0
Exec_Master_Log_Pos: 55848766
Relay_Log_Space: 13454938
Until_Condition: None
 Until_Log_File:
  Until_Log_Pos: 0
 Master_SSL_Allowed: No
 Master_SSL_CA_File:
 Master_SSL_CA_Path:
Master_SSL_Cert:
  Master_SSL_Cipher:
 Master_SSL_Key:
  Seconds_Behind_Master: 0
1 row in set (0.00 sec)
---

I get the folllowing on my mysql.err:
121205 15:09:56 [Note] Slave SQL thread initialized, starting replication
in log 'mysql-bin.000289' at position 42394063, relay log
'/var/log/mysql/mysql-relay-bin.01' position: 4
121205 15:09:56 [Note] Slave I/O thread: connected to master '
sdcwa_slave@192.168.1.21:3306',  replication started in log
'mysql-bin.000289' at position 42394063


Everything is GOOD, for a little while and then I get an error on mysql.err:

-

Now if I do the SKIP FLAG many times, I will error after error...
I do not see how replication works so well for others if I am using the
steps in the link
on top of this message.

THANKS!!!


On Wed, Dec 5, 2012 at 3:42 AM, Manuel Arostegui  wrote:

>
>
> 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 the
>> replication from the
>> beginning but I get the same problem after a while.
>>
>> Does anyone know a way to fix this?
>>
>>
> Hello,
>
> How did you build the slave from the master? How did you decide in which
> position the slave should start replicating from?
> You might want to try pt-table-checksum (
> http://www.percona.com/doc/percona-toolkit/2.1/pt-table-checksum.html) to
> see what else do you have broken.
>
> Manuel.
>
>
> --
> Manuel Aróstegui
> Systems Team

Re: MySQL Replication Error

[Igor Shevtsov]

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,
Igor


On 06/12/12 21:59, Néstor wrote:

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, referer,
hostname, timestamp)
 VALUES
 (0, 'page not found', 'images/internet_explorer/borderTopLeft.png',
'N;', 4, '','
http://www.sdcwa.org/es/images/internet_explorer/borderTopLeft.png', '',
'10.20.141.24', 1354754352)', Error_code: 1062
121205 16:39:51 [ERROR] Error running query, slave SQL thread aborted. Fix
the problem, and restart the slave SQL thread with "SLAVE START". We
stopped at log 'mysql-bin.000289' position 86451409


Sorry for the long message, below are the steps use to create my
replication.


When I created the replication, I followed the steps here :
http://crazytoon.com/2008/01/29/mysql-how-do-you-set-up-masterslave-replication-in-mysql-centos-rhel-fedora/
  I am on a red hat server.
---
I set my firewall to accept info from server1 on server2
SERVER1:
tcp0  0 wahoo.sdcwa.org:mysql   wahooesc.sdcwa.org:52131
  ESTABLISHED 30145/mysqld
SERVER2:
tcp0  0 wahooesc.sdcwa.org:52131www.sdcwa.org:mysql
ESTABLISHED 30875/mysqld
-

I have try using the SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;

I have also done these steps where in SERVER1
FLUSH TABLES WITH READ LOCK;
SHOW MASTER STATUS;
+--+--+--+--+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+--+--+--+--+
| mysql-bin.000289 | 42394063 |  |  |
+--+--+--+--+

Then Dump SERVER1 database then you unlock SERVER1 database
and copy it to SERVER2 then FLUSH TABLES WITH READ LOCK;

I proceed to STOP SLAVE then add the database to SERVER2 then
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000289',
MASTER_LOG_POS=42394063; to synch with the SERVER1
Then I start SERVER2 and the output of  slave status is:

mysql> SHOW SLAVE STATUS\G
*** 1. row ***
  Slave_IO_State: Waiting for master to send event
 Master_Host: 10.168.1.21
 Master_User: sdcwa_slave
 Master_Port: 3306
   Connect_Retry: 60
 Master_Log_File: mysql-bin.000289
 Read_Master_Log_Pos: 55848766
  Relay_Log_File: mysql-relay-bin.02
   Relay_Log_Pos: 13454938
   Relay_Master_Log_File: mysql-bin.000289
Slave_IO_Running: Yes
   Slave_SQL_Running: Yes
 Replicate_Do_DB:
 Replicate_Ignore_DB:
  Replicate_Do_Table:
  Replicate_Ignore_Table:
 Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
  Last_Errno: 0
  Last_Error:
Skip_Counter: 0
 Exec_Master_Log_Pos: 55848766
 Relay_Log_Space: 13454938
 Until_Condition: None
  Until_Log_File:
   Until_Log_Pos: 0
  Master_SSL_Allowed: No
  Master_SSL_CA_File:
  Master_SSL_CA_Path:
 Master_SSL_Cert:
   Master_SSL_Cipher:
  Master_SSL_Key:
   Seconds_Behind_Master: 0
1 row in set (0.00 sec)
---

I get the folllowing on my mysql.err:
121205 15:09:56 [Note] Slave SQL thread initialized, starting replication
in log 'mysql-bin.000289' at position 42394063, relay log
'/var/log/mysql/mysql-relay-bin.01' position: 4
121205 15:09:56 [Note] Slave I/O thread: connected to master '
sdcwa_slave@192.168.1.21:3306',  replication started in log
'mysql-bin.000289' at position 42394063


Everything is GOOD, for a little while and then I get an error on mysql.err:

-

Now if I do the SKIP FLAG many times, I will error after error...
I do not see how replication works so well for others if I am using the
steps in the link
on top of this message.

THANKS!!!


On Wed, Dec 5, 2012 at 3:42 AM, Manuel Arostegui  wrote:



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 the
replication from the
beginning but I get the same problem after a while.

Does anyone know a way to fix this?



Hello,

How did y

Re: MySQL Replication Error

[Néstor]

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-up-masterslave-replication-in-mysql-centos-rhel-fedora/

THANKS!!!

Nestor


On Wed, Dec 5, 2012 at 3:35 AM, Johan De Meersman wrote:

> - 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 exists" is not an indication of fitness for any specific
> use, and that kind of option is really only for use in very very specific
> cases where you KNOW what's wrong and KNOW that it's not harmful in your
> highly specific situation.
>
>
> --
> Linux Bier Wanderung 2012, now also available in Belgium!
> August, 12 to 19, Diksmuide, Belgium - http://lbw2012.tuxera.be
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/mysql
>
>

Re: MySQL Replication Error

[Manuel Arostegui]

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 the
> replication from the
> beginning but I get the same problem after a while.
>
> Does anyone know a way to fix this?
>
>
Hello,

How did you build the slave from the master? How did you decide in which
position the slave should start replicating from?
You might want to try pt-table-checksum (
http://www.percona.com/doc/percona-toolkit/2.1/pt-table-checksum.html) to
see what else do you have broken.

Manuel.


-- 
Manuel Aróstegui
Systems Team
tuenti.com

Re: MySQL Replication Error

[Johan De Meersman]

- 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 exists" is not an indication of fitness for any specific use, and 
that kind of option is really only for use in very very specific cases where 
you KNOW what's wrong and KNOW that it's not harmful in your highly specific 
situation.


-- 
Linux Bier Wanderung 2012, now also available in Belgium!
August, 12 to 19, Diksmuide, Belgium - http://lbw2012.tuxera.be

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

Re: MySQL Replication Error

[divesh kamra]

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
>
> 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
> as a binary copy of the stopped master and secured
> with "read-only"
>
>
>
>
>
>
>

Re: MySQL Replication Error

[Reindl Harald]

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
as a binary copy of the stopped master and secured
with "read-only"








signature.asc
Description: OpenPGP digital signature

RE: MySQL Replication Error

[Rick James]

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 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 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] Slave I/O thread killed while reading event
> 121130 12:41:53 [Note] Slave I/O thread exiting, read up to log 'mysql-
> bin.000266', position 76841310
> 121130 12:41:57 [Note] Slave SQL thread initialized, starting
> replication in log 'mysql-bin.000265' at position 99071761, relay log
> '/var/log/mysql/mysql-relay-bin.06' position: 98589371
> 121130 12:41:57 [Note] Slave I/O thread: connected to master '
> sdcwa_slave@10.168.1.21:3306',  replication started in log 'mysql-
> bin.000266' at position 76841310
> 121130 12:41:57 [ERROR] Slave: Error 'Duplicate entry 'links:primary-
> links:tree-data:7b7216a15969aa93e5dfb9aaa24bfc32' for key 1'
> on query. Default database: 'parallax'. Query: 'INSERT INTO cache_menu
> (cid, data, created, expire, headers, serialized) VALUES
> ('links:primary-links:tree-data:7b7216a15969aa93e5dfb9aaa24bfc32',
> 'a:2:{s:4:\"tree\";a:19:{i:310;a:2:{s:4:\"link\";a:38:{s:14:\"load_func
> tions\";s:26:\"a:1:{i:1;s:9:\"node_load\";}\";s:16:\"to_arg_functions\"
> ;s:0:\"\";s:15:\"access_callback\";s:11:\"node_access\";s:16:\"access_a
> rguments\";s:29:\"a:2:{i:0;s:4:\"view\";i:1;i:1;}\";s:13:\"page_callbac
> k\";s:14:\"node_page_view\";s:14:\"page_arguments\";s:14:\"a:1:{i:0;i:1
> ;}\";s:5:\"title\";s:0:\"\";s:14:\"title_callback\";s:15:\"node_page_ti
> tle\";s:15:\"title_arguments\";s:14:\"a:1:{i:0;i:1;}\";s:4:\"type\";s:1
> :\"4\";s:11:\"description\";s:0:\"\";s:9:\"menu_name\";s:13:\"primary-
> links\";s:4:\"mlid\";s:3:\"310\";s:4:\"plid\";s:1:\"0\";s:9:\"link_path
> \";s:7:\"node/14\";s:11:\"router_path\";s:6:\"node/%\";s:10:\"link_titl
> e\";s:11:\"Wh
> 121130 12:41:57 [ERROR] Error running query, slave SQL thread aborted.
> Fix the problem, and restart the slave SQL thread with "SLAVE START".
> We stopped at log 'mysql-bin.000265' position 99451408
> 
> I done searches on google and I look at several sites and basically
> they say to do the following:
> mysql> stop slave;
> mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; start slave; show slave
> mysql> status\G
> 
> But after doing this a couple of minutes later I get the same situation
> 
> 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 the replication from the beginning but I get the same problem
> after a while.
> 
> Does anyone know a way to fix this?
> 
> Thanks,
> 
> Néstor

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Replication Error

[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,
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] Slave I/O thread killed while reading event
121130 12:41:53 [Note] Slave I/O thread exiting, read up to log
'mysql-bin.000266', position 76841310
121130 12:41:57 [Note] Slave SQL thread initialized, starting replication
in log 'mysql-bin.000265' at position 99071761, relay log
'/var/log/mysql/mysql-relay-bin.06' position: 98589371
121130 12:41:57 [Note] Slave I/O thread: connected to master '
sdcwa_slave@10.168.1.21:3306',  replication started in log
'mysql-bin.000266' at position 76841310
121130 12:41:57 [ERROR] Slave: Error 'Duplicate entry
'links:primary-links:tree-data:7b7216a15969aa93e5dfb9aaa24bfc32' for key 1'
on query. Default database: 'parallax'. Query: 'INSERT INTO cache_menu
(cid, data, created, expire, headers, serialized) VALUES
('links:primary-links:tree-data:7b7216a15969aa93e5dfb9aaa24bfc32',
'a:2:{s:4:\"tree\";a:19:{i:310;a:2:{s:4:\"link\";a:38:{s:14:\"load_functions\";s:26:\"a:1:{i:1;s:9:\"node_load\";}\";s:16:\"to_arg_functions\";s:0:\"\";s:15:\"access_callback\";s:11:\"node_access\";s:16:\"access_arguments\";s:29:\"a:2:{i:0;s:4:\"view\";i:1;i:1;}\";s:13:\"page_callback\";s:14:\"node_page_view\";s:14:\"page_arguments\";s:14:\"a:1:{i:0;i:1;}\";s:5:\"title\";s:0:\"\";s:14:\"title_callback\";s:15:\"node_page_title\";s:15:\"title_arguments\";s:14:\"a:1:{i:0;i:1;}\";s:4:\"type\";s:1:\"4\";s:11:\"description\";s:0:\"\";s:9:\"menu_name\";s:13:\"primary-links\";s:4:\"mlid\";s:3:\"310\";s:4:\"plid\";s:1:\"0\";s:9:\"link_path\";s:7:\"node/14\";s:11:\"router_path\";s:6:\"node/%\";s:10:\"link_title\";s:11:\"Wh
121130 12:41:57 [ERROR] Error running query, slave SQL thread aborted. Fix
the problem, and restart the slave SQL thread with "SLAVE START". We
stopped at log 'mysql-bin.000265' position 99451408

I done searches on google and I look at several sites and basically they
say to do the following:
mysql> stop slave;
mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;
mysql> start slave;
mysql> show slave status\G

But after doing this a couple of minutes later I get the same situation

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 the
replication from the
beginning but I get the same problem after a while.

Does anyone know a way to fix this?

Thanks,

Néstor

RE: mysql replication error

[Natale Babbo]

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?
> 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: 10/23/02 8:22 AM
> Subject: mysql replication error
> 
> 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 PROTECTED]:3306',  replication started in log
> 'FIRST' at position 4
> 021023 14:08:35  Error updating slave list: Query
> error
> 021023 14:08:35  Slave I/O thread exiting, read up
> to
> log 'FIRST', position 4
> 
> what does it mean?
> 
> My.ini on Master:
> log-bin=C:\Programmi\MySQL\Logs\MySQL-bin
> server-id=1
> 
> My.ini on Slave:
> master-host=192.168.0.4
> master-user=repl
> master-password=
> master-port=3306
> server-id=2
> set-variable = slave_net_timeout=3600
> set-variable = net_read_timeout=3600
> 
> Show master status:
> File : MySQL-bin.001
> Position : 79
> Binlog_do_db : 
> Binlog_inogne_db :
> 
> ERROR
> No query specified
> 
> Show Slave status:
> Master_Host  : 192.168.0.04
> Master_User  : repl
> Master_Port  : 3306
> Connect_retry: 60
> Master_Log_File  : 
> Read_Master_Log_Pos  : 4
> Relay_Log_File   : MySQL-relay-bin.002
> Relay_Log_Pos: 4
> Relay_Master_Log_File: 
> Slave_IO_Running : Yes
> Slave_SQL_Running: Yes
> Replicate_do_db  : 
> Replicate_ignore_db  : 
> Last_errno   : 0
> Last_error   : 
> Skip_counter : 0
> Exec_master_log_pos  : 0
> Relay_log_space  : 0
> 
> ERROR:
> No query specified
> 
> What is wrong?
> Why do I get the error ? Which
> type of query should I specify?
> 
> Thanks in advance.
> Natale Babbo
> 
>
__
> Mio Yahoo!: personalizza Yahoo! come piace a te 
>
http://it.yahoo.com/mail_it/foot/?http://it.my.yahoo.com/
> 
>
-
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list
> archive)
> 
> To request this thread, e-mail
> <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
>
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try:
http://lists.mysql.com/php/unsubscribe.php 

__
Mio Yahoo!: personalizza Yahoo! come piace a te 
http://it.yahoo.com/mail_it/foot/?http://it.my.yahoo.com/

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

mysql replication error

[Natale Babbo]

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 PROTECTED]:3306',  replication started in log
'FIRST' at position 4
021023 14:08:35  Error updating slave list: Query
error
021023 14:08:35  Slave I/O thread exiting, read up to
log 'FIRST', position 4

what does it mean?

My.ini on Master:
log-bin=C:\Programmi\MySQL\Logs\MySQL-bin
server-id=1

My.ini on Slave:
master-host=192.168.0.4
master-user=repl
master-password=
master-port=3306
server-id=2
set-variable = slave_net_timeout=3600
set-variable = net_read_timeout=3600

Show master status:
File : MySQL-bin.001
Position : 79
Binlog_do_db : 
Binlog_inogne_db :

ERROR
No query specified

Show Slave status:
Master_Host  : 192.168.0.04
Master_User  : repl
Master_Port  : 3306
Connect_retry: 60
Master_Log_File  : 
Read_Master_Log_Pos  : 4
Relay_Log_File   : MySQL-relay-bin.002
Relay_Log_Pos: 4
Relay_Master_Log_File: 
Slave_IO_Running : Yes
Slave_SQL_Running: Yes
Replicate_do_db  : 
Replicate_ignore_db  : 
Last_errno   : 0
Last_error   : 
Skip_counter : 0
Exec_master_log_pos  : 0
Relay_log_space  : 0

ERROR:
No query specified

What is wrong?
Why do I get the error ? Which
type of query should I specify?

Thanks in advance.
Natale Babbo

__
Mio Yahoo!: personalizza Yahoo! come piace a te 
http://it.yahoo.com/mail_it/foot/?http://it.my.yahoo.com/

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: mysql replication (Error reading packet from server: Binary logis not open (read_errno 0,server_errno=2000)

[gerald_clark]

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  Error reading packet from server: Binary log is not open
>(read_errno 0,server_errno=2000)
>021009 12:56:49  Slave: Failed reading log event, reconnecting to retry, log
>'FIRST' position 4
>021009 12:56:49  Slave: reconnected to master
>'[EMAIL PROTECTED]:3306',replication resumed 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)
>
>
>Im doing mysql replication, i cant figure this error "Binary log is not
>open" ?
>
>
>
>--
>thanks,
>louie miranda
>chikka asia, inc.
>noc +63-2(7535000-511)
>
>
>-
>Before posting, please check:
>   http://www.mysql.com/manual.php   (the manual)
>   http://lists.mysql.com/   (the list archive)
>
>To request this thread, e-mail <[EMAIL PROTECTED]>
>To unsubscribe, e-mail 
><[EMAIL PROTECTED]>
>Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
>  
>



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

mysql replication (Error reading packet from server: Binary log is not open (read_errno 0,server_errno=2000)

[louie miranda]

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)
021009 12:56:49  Slave: Failed reading log event, reconnecting to retry, log
'FIRST' position 4
021009 12:56:49  Slave: reconnected to master
'[EMAIL PROTECTED]:3306',replication resumed 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)


Im doing mysql replication, i cant figure this error "Binary log is not
open" ?



--
thanks,
louie miranda
chikka asia, inc.
noc +63-2(7535000-511)


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MySQL replication error

[Luc Foisy]

That's pretty strange in this situation, we have three slaves being updated
from the master, the other two are moving along just fine.
This one however can't seem to get past these "duplicate entries". I tried
skip_counter=2 and got a different duplicate entry, the possition moving
forward
again. Incresed skip_counter again... Now the slave is running, but not
going anywhere, slave position is like 2.5 million where the master is at
about 17 million. Bah, I think i'll just start this slave over again from
the base, unfortunately there is a great deal of catching 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 replication somewhere an update was taken
twice.  Adjust the skip to according to the position of the duplicate entry.
I have had to skip 100 before in order to get the slave started.

First check the binary log and see how many insert statements after
the error "path to mysql/bin/mysqlbinlog QBSLIXDB1-bin.log".  There had to
be a reason why the rep stop syncing ( did you run a myisam check on the
master and it removed something??).  Check the log to see what transaction
failed or duplicated itself.  Normally you can skip that transaction on the
slave and start up the slave.  But if therea are other transaction out of
sync after the first failed transaction you will have to keep skipping the
transactions. Until the slave kicks up.  

 It kinda hard to tell with out seeing the binary log file as to how
many you have to skip or even which one to skip.

  But as soon as you hit the duplicate transaction witht he skip, the slave
will start.

  Let me know the scoop...

-chad
  

On Fri, 22 Feb 2002 11:29:41 -0500
Luc Foisy <[EMAIL PROTECTED]> wrote:

> 
> Chad, this did not work. Though it did do something, the Position jumped
> ahead
> 
> mysql> show slave status\G
> *** 1. row ***
> Master_Host: 209.217.92.34
> Master_User: repslave2
> Master_Port: 3306
>   Connect_retry: 60
>Log_File: QBSLXDB1-bin.029
> Pos: 2596608
>   Slave_Running: No
> Replicate_do_db: qbslive
> Replicate_ignore_db:
>  Last_errno: 1062
>  Last_error: error 'Duplicate entry '1376034' for key 1' on query
> 'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())'
>Skip_counter: 1
> 1 row in set (0.00 sec)
> 
> mysql> set sql_slave_skip_counter = 1;
> Query OK, 0 rows affected (0.01 sec)
> 
> mysql> slave start;
> Query OK, 0 rows affected (0.00 sec)
> 
> mysql> show slave status\G
> *** 1. row ***
> Master_Host: 209.217.92.34
> Master_User: repslave2
> Master_Port: 3306
>   Connect_retry: 60
>Log_File: QBSLXDB1-bin.029
> Pos: 2596630
>   Slave_Running: No
> Replicate_do_db: qbslive
> Replicate_ignore_db:
>  Last_errno: 1062
>  Last_error: error 'Duplicate entry '1376034' for key 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 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 long as you are sure the master is ok.
> 
> Let me know is this worked.
> 
> -chad
> 
> 
> 
> On Thu, 21 Feb 2002 15:48:08 -0500
> Luc Foisy <[EMAIL PROTECTED]> wrote:
> 
> > 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_File: QBSLXDB1-bin.029
> > Pos: 2596608
> >   Slave_Running: No
> > Replicate_do_db: qbslive
> > Replicate_ignore_db:
> >  Last_errno: 1062
> >  Last_error: error 'Duplicate entry '1376034' for key 1' on
query
&g

Re: MySQL replication error

[chad kellerman]

Luc,

The problem is that in the replication somewhere an update was taken twice.  
Adjust the skip to according to the position of the duplicate entry.  I have had to 
skip 100 before in order to get the slave started.

First check the binary log and see how many insert statements after the error 
"path to mysql/bin/mysqlbinlog QBSLIXDB1-bin.log".  There had to be a reason why the 
rep stop syncing ( did you run a myisam check on the master and it removed 
something??).  Check the log to see what transaction failed or duplicated itself.  
Normally you can skip that transaction on the slave and start up the slave.  But if 
therea are other transaction out of sync after the first failed transaction you will 
have to keep skipping the transactions. Until the slave kicks up.  

 It kinda hard to tell with out seeing the binary log file as to how many you have 
to skip or even which one to skip.

  But as soon as you hit the duplicate transaction witht he skip, the slave will start.

  Let me know the scoop...

-chad
  

On Fri, 22 Feb 2002 11:29:41 -0500
Luc Foisy <[EMAIL PROTECTED]> wrote:

> 
> Chad, this did not work. Though it did do something, the Position jumped
> ahead
> 
> mysql> show slave status\G
> *** 1. row ***
> Master_Host: 209.217.92.34
> Master_User: repslave2
> Master_Port: 3306
>   Connect_retry: 60
>Log_File: QBSLXDB1-bin.029
> Pos: 2596608
>   Slave_Running: No
> Replicate_do_db: qbslive
> Replicate_ignore_db:
>  Last_errno: 1062
>  Last_error: error 'Duplicate entry '1376034' for key 1' on query
> 'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())'
>Skip_counter: 1
> 1 row in set (0.00 sec)
> 
> mysql> set sql_slave_skip_counter = 1;
> Query OK, 0 rows affected (0.01 sec)
> 
> mysql> slave start;
> Query OK, 0 rows affected (0.00 sec)
> 
> mysql> show slave status\G
> *** 1. row ***
> Master_Host: 209.217.92.34
> Master_User: repslave2
> Master_Port: 3306
>   Connect_retry: 60
>Log_File: QBSLXDB1-bin.029
> Pos: 2596630
>   Slave_Running: No
> Replicate_do_db: qbslive
> Replicate_ignore_db:
>  Last_errno: 1062
>  Last_error: error 'Duplicate entry '1376034' for key 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 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 long as you are sure the master is ok.
> 
> Let me know is this worked.
> 
> -chad
> 
> 
> 
> On Thu, 21 Feb 2002 15:48:08 -0500
> Luc Foisy <[EMAIL PROTECTED]> wrote:
> 
> > 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_File: QBSLXDB1-bin.029
> > Pos: 2596608
> >   Slave_Running: No
> > Replicate_do_db: qbslive
> > Replicate_ignore_db:
> >  Last_errno: 1062
> >  Last_error: error 'Duplicate entry '1376034' for key 1' on query
> > 'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())'
> >Skip_counter: 0
> > 
> > err_log
> > 020221 14:21:12  mysqld started
> > /usr/local/libexec/mysqld: ready for connections
> > 020221 14:21:14  Slave: connected to master
> '[EMAIL PROTECTED]:3306',
> > replication started in log 'QBSLXDB1-bin.029' at position
> > 2596608
> > ERROR: 1062  Duplicate entry '1376034' for key 1
> > 020221 14:21:14  Slave:  error running query 'INSERT INTO DISPATCHLOG
> > (CreateStamp) VALUES (NOW())'
> > 020221 14:21:14  Error running query, slave aborted. Fix the problem, and
> > re-start the slave thread with "mysqladmin start-slave". We s
> > topped at log 'QBSLXDB1-b

RE: MySQL replication error

[Luc Foisy]

Chad, this did not work. Though it did do something, the Position jumped
ahead

mysql> show slave status\G
*** 1. row ***
Master_Host: 209.217.92.34
Master_User: repslave2
Master_Port: 3306
  Connect_retry: 60
   Log_File: QBSLXDB1-bin.029
Pos: 2596608
  Slave_Running: No
Replicate_do_db: qbslive
Replicate_ignore_db:
 Last_errno: 1062
 Last_error: error 'Duplicate entry '1376034' for key 1' on query
'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())'
   Skip_counter: 1
1 row in set (0.00 sec)

mysql> set sql_slave_skip_counter = 1;
Query OK, 0 rows affected (0.01 sec)

mysql> slave start;
Query OK, 0 rows affected (0.00 sec)

mysql> show slave status\G
*** 1. row ***
Master_Host: 209.217.92.34
Master_User: repslave2
Master_Port: 3306
  Connect_retry: 60
   Log_File: QBSLXDB1-bin.029
Pos: 2596630
  Slave_Running: No
Replicate_do_db: qbslive
Replicate_ignore_db:
 Last_errno: 1062
 Last_error: error 'Duplicate entry '1376034' for key 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 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 long as you are sure the master is ok.

Let me know is this worked.

-chad



On Thu, 21 Feb 2002 15:48:08 -0500
Luc Foisy <[EMAIL PROTECTED]> wrote:

> 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_File: QBSLXDB1-bin.029
> Pos: 2596608
>   Slave_Running: No
> Replicate_do_db: qbslive
> Replicate_ignore_db:
>  Last_errno: 1062
>  Last_error: error 'Duplicate entry '1376034' for key 1' on query
> 'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())'
>Skip_counter: 0
> 
> err_log
> 020221 14:21:12  mysqld started
> /usr/local/libexec/mysqld: ready for connections
> 020221 14:21:14  Slave: connected to master
'[EMAIL PROTECTED]:3306',
> replication started in log 'QBSLXDB1-bin.029' at position
> 2596608
> ERROR: 1062  Duplicate entry '1376034' for key 1
> 020221 14:21:14  Slave:  error running query 'INSERT INTO DISPATCHLOG
> (CreateStamp) VALUES (NOW())'
> 020221 14:21:14  Error running query, slave aborted. Fix the problem, and
> re-start the slave thread with "mysqladmin start-slave". We s
> topped at log 'QBSLXDB1-bin.029' position 2596608
> 020221 14:21:14  Slave thread exiting, replication stopped in log
> 'QBSLXDB1-bin.029' at position 2596608
> 
> 
> Luc Foisy
> 
> Technical Magic - www.technical-magic.com
> 1 Stafford Road, Suite 325, Nepean, Ontario, K2H 1B9
> Phone: (613) 829-7117 Fax: (613) 596-5096
> E-Mail: [EMAIL PROTECTED]
> 
> <<<<< Fulfilling the Promise of Technology >>>>>
> 
> 
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
> 
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> 

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL replication error

[chad kellerman]

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 Feb 2002 15:48:08 -0500
Luc Foisy <[EMAIL PROTECTED]> wrote:

> 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_File: QBSLXDB1-bin.029
> Pos: 2596608
>   Slave_Running: No
> Replicate_do_db: qbslive
> Replicate_ignore_db:
>  Last_errno: 1062
>  Last_error: error 'Duplicate entry '1376034' for key 1' on query
> 'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())'
>Skip_counter: 0
> 
> err_log
> 020221 14:21:12  mysqld started
> /usr/local/libexec/mysqld: ready for connections
> 020221 14:21:14  Slave: connected to master '[EMAIL PROTECTED]:3306',
> replication started in log 'QBSLXDB1-bin.029' at position
> 2596608
> ERROR: 1062  Duplicate entry '1376034' for key 1
> 020221 14:21:14  Slave:  error running query 'INSERT INTO DISPATCHLOG
> (CreateStamp) VALUES (NOW())'
> 020221 14:21:14  Error running query, slave aborted. Fix the problem, and
> re-start the slave thread with "mysqladmin start-slave". We s
> topped at log 'QBSLXDB1-bin.029' position 2596608
> 020221 14:21:14  Slave thread exiting, replication stopped in log
> 'QBSLXDB1-bin.029' at position 2596608
> 
> 
> Luc Foisy
> 
> Technical Magic - www.technical-magic.com
> 1 Stafford Road, Suite 325, Nepean, Ontario, K2H 1B9
> Phone: (613) 829-7117 Fax: (613) 596-5096
> E-Mail: [EMAIL PROTECTED]
> 
> < Fulfilling the Promise of Technology >
> 
> 
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
> 
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> 

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

MySQL replication error

[Luc Foisy]

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_File: QBSLXDB1-bin.029
Pos: 2596608
  Slave_Running: No
Replicate_do_db: qbslive
Replicate_ignore_db:
 Last_errno: 1062
 Last_error: error 'Duplicate entry '1376034' for key 1' on query
'INSERT INTO DISPATCHLOG (CreateStamp) VALUES (NOW())'
   Skip_counter: 0

err_log
020221 14:21:12  mysqld started
/usr/local/libexec/mysqld: ready for connections
020221 14:21:14  Slave: connected to master '[EMAIL PROTECTED]:3306',
replication started in log 'QBSLXDB1-bin.029' at position
2596608
ERROR: 1062  Duplicate entry '1376034' for key 1
020221 14:21:14  Slave:  error running query 'INSERT INTO DISPATCHLOG
(CreateStamp) VALUES (NOW())'
020221 14:21:14  Error running query, slave aborted. Fix the problem, and
re-start the slave thread with "mysqladmin start-slave". We s
topped at log 'QBSLXDB1-bin.029' position 2596608
020221 14:21:14  Slave thread exiting, replication stopped in log
'QBSLXDB1-bin.029' at position 2596608


Luc Foisy

Technical Magic - www.technical-magic.com
1 Stafford Road, Suite 325, Nepean, Ontario, K2H 1B9
Phone: (613) 829-7117 Fax: (613) 596-5096
E-Mail: [EMAIL PROTECTED]

< Fulfilling the Promise of Technology >


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php