Based on the SHOW SLAVE STATUS output you've sent us, I'd suggest that you
check what the application is doing, understand *why* the application is
violating the PK of the table information_server.audit, repair the possible
application problem and the, reconfigure the replication.
It seems that there's something not really good happening on the
application side since the error 1062 is being threw out by a INSERT sent
to the database ... by the application.
*PS.: looking at the purpose of information_server.audit, I wonder if this
is not a *design* problem!*
1-) Fix the application if you can, investigating the problem the
replication is showing up on SHOW SLAVE STATUS - remember that the
column Last_SQL_Error
is one of SHOW SLAVE STATUS best friends in this context;
2-) After to fix the problem, if design or application, recreate the slave
and then, start replication again;
It's possible to use another things to make the replication to bypass this
kind of problem, but, it's not that cool to have it configured. due to
that, I'd like to omit it at this point.
Let's keep in touch, happy mysql'ing!!
--
*Wagner Bianchi*
2014-08-30 9:54 GMT-03:00 Johnny Withers <joh...@pixelated.net>:
> There's a duplicate key on the audit table, 18699. Delete it and restart
> slave (start slave). Check slave status again, might be more rows in there
> duplicated.
>
> You might want to compare the row to master to ensure it's a duplicate
> before deleting from slave.
> On Aug 30, 2014 7:52 AM, "william drescher" <will...@techservsys.com>
> wrote:
>
> > On 8/29/2014 7:40 PM, Suresh Kuna wrote:
> >
> >> You can paste the show slave status\G here for us to review and on
> >> Master,
> >> show global variables like 'log-bin%'; show master status ( 3 to 4 times
> >> continuously )
> >>
> > after a more complex transaction;
> > +------------------+----------+--------------+------------------+
> > | File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
> > +------------------+----------+--------------+------------------+
> > | mysql-bin.001225 | 5952 | | |
> > +------------------+----------+--------------+------------------+
> >
> > *************************** 1. row ***************************
> > Slave_IO_State: Waiting for master to send event
> > Master_Host: 192.168.10.101
> > Master_User: repl
> > Master_Port: 3306
> > Connect_Retry: 60
> > Master_Log_File: mysql-bin.001225
> > Read_Master_Log_Pos: 5952
> > Relay_Log_File: ubuntu2-relay-bin.000002
> > Relay_Log_Pos: 16426
> > Relay_Master_Log_File: mysql-bin.001139
> > 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 '18699' for key
> > 'PRIMARY'' on query. Default database: 'Information_server'. Query:
> 'insert
> > into audit (audit_type, subtype, user_Id, ptNum, data) values ('login',
> > 'login', 'WPD', 0, 'Login: WPD from location: Suite B')'
> > Skip_Counter: 0
> > Exec_Master_Log_Pos: 90012430
> > Relay_Log_Space: 29733455
> > 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: 1062
> > Last_SQL_Error: Error 'Duplicate entry '18699' for key
> > 'PRIMARY'' on query. Default database: 'Information_server'. Query:
> 'insert
> > into audit (audit_type, subtype, user_Id, ptNum, data) values ('login',
> > 'login', 'WPD', 0, 'Login: WPD from location: Suite B')'
> > Replicate_Ignore_Server_Ids:
> > Master_Server_Id: 3
> >
> >
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe: http://lists.mysql.com/mysql
> >
> >
>
