# Replication to slave stops with "Error: Duplicate entry"

**URL:** <https://forums.percona.com/t/replication-to-slave-stops-with-error-duplicate-entry/1163>\
**Category:** Other MySQL® Questions\
**Created:** [May 1, 2009, 12:07pm UTC](https://forums.percona.com/t/replication-to-slave-stops-with-error-duplicate-entry/1163 "2009-05-01T12:07:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulchoi](https://avatars.discourse-cdn.com/v4/letter/p/f1d935/32.png) [@paulchoi](https://forums.percona.com/u/paulchoi)\
**Post date:** [May 1, 2009, 12:07pm UTC](https://forums.percona.com/t/replication-to-slave-stops-with-error-duplicate-entry/1163/1 "2009-05-01T12:07:00Z")

</div>

Replication to the slave keeps on failing. Even if I delete the conflicted entry on the slave and issue START SLAVE, the error pops up after a few seconds.

The slave is not being used for anything right now, not even for reads.

We’re running MySQL 5.0.75, the Percona version with XtraDB. The OS is OpenSolaris.

mysql\> show slave status \G  
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* 1. row \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Slave\_IO\_State: Waiting for master to send event  
Master\_Host: dp03a  
Master\_User: repl  
Master\_Port: 6614  
Connect\_Retry: 60  
Master\_Log\_File: binlog.002015  
Read\_Master\_Log\_Pos: 1530491  
Relay\_Log\_File: relay.000020  
Relay\_Log\_Pos: 8458621  
Relay\_Master\_Log\_File: binlog.001553  
Slave\_IO\_Running: Yes  
Slave\_SQL\_Running: No  
Replicate\_Do\_DB:  
Replicate\_Ignore\_DB:  
Replicate\_Do\_Table:  
Replicate\_Ignore\_Table:  
Replicate\_Wild\_Do\_Table:  
Replicate\_Wild\_Ignore\_Table:  
Last\_Errno: 1062  
Last\_Error: Error ‘Duplicate entry ‘206159784376-464033’ for key 2’ on query. Default database: ‘pulse\_user48’. Query: ‘INSERT INTO plx\_ab\_feed (plx\_ab\_feed.uhid, plx\_ab\_feed.feed\_id, plx\_ab\_feed.display\_id, plx\_ab\_feed.entry\_id, plx\_ab\_feed.last\_updated) VALUES (“206159784376”, “464033”, “”, “54608808”, now())’  
Skip\_Counter: 0  
Exec\_Master\_Log\_Pos: 8458487  
Relay\_Log\_Space: 4880870001  
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: NULL  
1 row in set (0.00 sec)

mysql\>

We’re also seeing “Lock wait timeout” errors on a couple of other slaves doing replication. These slaves are doing nothing but replicating the master (so no read from the slaves). They’re also running Percona’s MySQL 5.0.75 with XtraDB build. Supposedly this bug was fixed in 5.0.33 ([URL][MySQL Bugs: #20697: slave fails to rollback replicated transaction hang over innodb\_lock\_wait\_timeou](http://bugs.mysql.com/bug.php?id=20697%5B/URL%5D)), and we’re wondering if it’s a regression. I don’t know if this problem is related to the Duplicate Key error, but I’m just throwing it in there.

Any ideas what we should look for? Any help would be appreciated. Thanks in advance.
