Home / server / Questions / 336888
In Process
quanta
Asked: 2011-12-02 19:43:06 +0800 CST

What causes the MySQL error 1062 - duplicate entry when starting slave?

  • 772
  • MySQL Master version: 5.5.16-1
  • MySQL Slave version: 5.5.18-1

The master's snapshot is created by:

mysql> FLUSH TABLES WITH READ LOCK;
shell> mysqldump --all-databases --master-data > dbname_`date +%F`.sql

This dump file is imported on the slave (which is started with --skip-slave-start option) without error:

shell> pv dbname_`date +%F`.sql | mysql -u root -p

But I got the following error when executing the mysql> start slave;: 

    Last_SQL_Errno: 1062
    Last_SQL_Error: Error 'Duplicate entry '115846' for key
'PRIMARY'' on query. Default database: 'db'. Query: 'INSERT INTO
request_posted (id, user_id, channel, message, link, picture, name, ...

There is only one record with ID 115846 on the master:

mysql> select count(*) from request_posted where id=115846;
Current database: db

+----------+
| count(*) |
+----------+
|        1 |
+----------+
1 row in set (0.01 sec)

Try to skip some queries with:

mysql> STOP SLAVE; 
mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; 
mysql> START SLAVE;

didn't help. I don't want to skip those errors by adding:

slave-skip-errors = 1062

to my.cnf file because it may bring slave inconsistent.

What may be the reason for this error?

UPDATE

This is not how I usually setup mySQL replication

Which steps that you think I don't follow the document?

I wonder if you will encounter the same problem if you were to setup the entire configuration rather that passing the mysqldump command.

No, it works as normally if I also change the master to corresponding coordinates.

I would try dropping the database on the slave, make sure the binlogs are clear, and start again. Also check the table in question on the master to assure the indexes do not have errors.

Is delete (move) all the datadir enough? I did that and get the same result.

Reply to @Dmytro Leonenko

'show slave status\G' on slave to ensure that it is properly configured, MASTER_LOG_POS is 0

Only 'show slave statug\G' after import but before 'start slave;' can give us the answer

I backed up the datadir, delete all and run mysql_install_db, import the dump file, execute change master to and here's the results:

mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: 
                  Master_Host: x.x.x.x
                  Master_User: xx
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: 
          Read_Master_Log_Pos: 4
               Relay_Log_File: mysqld-relay-bin.000001
                Relay_Log_Pos: 4
        Relay_Master_Log_File: 
             Slave_IO_Running: No
            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: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 0
              Relay_Log_Space: 106
              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
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
1 row in set (0.00 sec)

I'm wondering why Master_Log_Pos is 4?

mysql mysql-replication

6 Answers

  1. What to try to fix your problem:

    1. You should remove master.info on slave first and restart mysql
    2. issue CHANGE MASTER TO MASTER_HOST='XX.XX.XX.XX', MASTER_USER='repl', MASTER_PASSWORD='slavepass';
    3. do mysqldump with '--flush-logs' option on master
    4. 'mysql -u user -p < dump.sql' on slave
    5. 'show slave status\G' on slave to ensure that it is properly configured, MASTER_LOG_POS is 0
    6. 'start slave;' on slave.

    What to check also:

    • Binlog format: MIXED
    • server_ids are different on master and slave
    • 8

  2. The problem is caused by setting up the master on a running production server BEFORE doing the dump (as far as I can tell). So, there are queries written in the master_log that have already been executed on the data residing on the slave. I never actually saw a solution on the mysql website or mailing list. So, I came up with the following solution that solved my problem.

    on slave:

    mysql> STOP SLAVE;
mysql> FLUSH PRIVILEGES;  # dump likly included users too

    on master:

    mysql> RESET MASTER;

    on slave: 

    mysql> RESET SLAVE;
mysql> START SLAVE;

    by the way, I ran my dump with the following on the slave: 

    mysqldump -uROOTUSER -pROOTPASSWORD -hMYSQLMASTER.EXAMPLE.COM --all-databases --delete-master-logs | mysql -uROOTUSER -pROOTPASSWORD

    I hope this helps someone else.

    http://dev.mysql.com/doc/refman/5.0/en/reset-master.html

    http://dev.mysql.com/doc/refman/5.0/en/reset-slave.html

    • 5

  3. If you don't want REDO the complete procedure, a good fix would be to use 

    STOP SLAVE;    
SET GLOBAL sql_slave_skip_counter=1;
START SLAVE;

    If there are too many such errors, a good idea would be to automate it using a bash script.

    Ref: Fixing Duplicate Entry Error

    • 3

  4. I had the exact problem and Ut xd's link helped. but the command in that link had syntax error and here is the version that worked for me:

    while [ 1 ]; do if [ `mysql -uroot -ppassword -e"show slave status \G;" | grep "Duplicate entry" | wc -l` -eq 2 ] ; then mysql -uroot -ppassword -e"stop slave; set global sql_slave_skip_counter=1; start slave;"; fi; sleep 1; mysql -uroot -ppassword -e"show slave status\G"; done

    It basically checks if there is duplicate entry error and skip this event from master. and do it in a loop.

    • 1

  5. In my case the issue is resolved by the following commands

    by the following steps

    STOP SLAVE;
RESET SLAVE;
START SLAVE;
    • 0

  6. to bypass the duplicate record at Mysql Slave DB, you can simply put an entry in /etc/my.cnf file on the slave DB as:

    slave-skip-errors = 1062
    • 0