C.2. Error/Cause/Solution

C.2.1. Replicator reports an Out of Memory error
C.2.2. pendingExceptionMessage": "Unable to update last commit seqno: Incorrect datetime value: '2016-03-13 02:02:26' for column 'update_timestamp' at row 1
C.2.4. Triggers not firing correctly on slave
C.2.5. Backup/Restore is not being my host back to normal
C.2.6. Lots of entries added to replicator log
C.2.7. Starting replication after performing a restore because of an invalid restart sequence number
C.2.8. Services requires a reset
C.2.9. ERROR 1010 (HY000) at line 5094506: Error dropping database (can't rmdir './mysql-bin/', errno: 17)
C.2.10. Connector shows errors with "java.net.SocketException: Broken pipe"
C.2.11. Too many open processes or files
C.2.12. Replicator fails to connect after updating password
C.2.13. Missing events, or events not extracted correctly
C.2.14. ERROR 1580 (HY000) at line 5093787: You cannot 'DROP' a log table if logging is enabled
C.2.15. Attempt to write new log record with equal or lower fragno: seqno=3 previous stored fragno=32767 attempted new fragno=-32768
C.2.16. cctrl reports MANAGER(state=STOPPED)
C.2.17. Latency is high: master:ONLINE, progress=41331580333, THL latency=78849.733
C.2.18. Unable to update the configuration of an installed directory
C.2.19. MySQL is incorrectly configured
C.2.20. trepctl status hangs
C.2.21. ERROR 2013 (HY000) at line 583: Lost connection to MySQL server during query
C.2.22. Backup agent name not found: xtrabackup-full
C.2.23. Event application failed: seqno=20725782 fragno=0 message=java.sql.SQLDataException: Data too long for column 'eventid' at row 1
C.2.24. cctrl hangs
C.2.25. [S1000][unixODBC][MySQL][ODBC 5.3(w) Driver]SSL connection error: unknown error number [ISQL]ERROR: Could not SQLConnect
C.2.26. WARN [KeepAliveTimerTask] - Error while sending a KEEP_ALIVE query to connection.
C.2.27. element 'mysql_readonly' not found in path
C.2.28. There were issues configuring the sandbox MySQL server
C.2.29. Error: could not settle on encryption_client algorithm
C.2.30. Replication latency very high
C.2.31. The master replicator stopped with a JDBC error.
C.2.32. Replicator runs out of memory