Tungsten
Clustering
Tungsten
Replicator
Tungsten
Dashboard
Contact Us
Get Support
Continuent Documentation
Manual Home
Tungsten Clustering (for MySQL) 5.3 Manual
Page in Other Manuals
Tungsten Replicator 5.3 Manual
Breadcrumbs
>
Tungsten Clustering (for MySQL) 5.3 Manual
>
C. Troubleshooting
Chapters
Preface
1. Introduction
2. Deployment
3. Deployment: MySQL Topologies
4. Deployment: Advanced
5. Operations Guide
6. Tungsten Connector
7. Tungsten Manager
8. Command-line Tools
9. The tpm Deployment Command
10. Replication Filters
11. Performance, Tuning and Testing
A. Release Notes
B. Prerequisites
C. Troubleshooting
D. Files, Directories, and Environment
E. Terminology Reference
F. Internals
G. Frequently Asked Questions (FAQ)
H. Ecosystem Support
I. Configuration Property Reference
Navigate Up
C. Troubleshooting
Parent Sections
C.1. Contacting Support
C.2. Error/Cause/Solution
C.3. Known Issues
C.4. Troubleshooting Timeouts
C.5. Troubleshooting Backups
C.6. Running Out of Diskspace
C.7. Troubleshooting SSH and tpm
C.8. Troubleshooting Data Differences
C.9. Comparing Table Data
C.10. Troubleshooting Memory Usage
C.2. Error/Cause/Solution
Prev
Appendix C. Troubleshooting
Next
C.2. Error/Cause/Solution
C.2.1.
[S1000][unixODBC][MySQL][ODBC 5.3(w) Driver]SSL connection error: unknown error number [ISQL]ERROR: Could not SQLConnect
C.2.2.
Replicator reports an Out of Memory error
C.2.3.
Too many open processes or files
C.2.4.
Latency is high: master:ONLINE, progress=41331580333, THL latency=78849.733
C.2.5.
WARNING: An illegal reflective access operation has occurred
C.2.6.
Missing events, or events not extracted correctly
C.2.7.
Replication latency very high
C.2.8.
Backup agent name not found: xtrabackup-full
C.2.9.
ERROR 2013 (HY000) at line 583: Lost connection to MySQL server during query
C.2.10.
Unable to update the configuration of an installed directory
C.2.11.
MySQL is incorrectly configured
C.2.12.
Replicator runs out of memory
C.2.13.
Services requires a reset
C.2.14.
Lots of entries added to replicator log
C.2.15.
cctrl hangs
C.2.16.
cctrl reports MANAGER(state=STOPPED)
C.2.17.
Attempt to write new log record with equal or lower fragno: seqno=3 previous stored fragno=32767 attempted new fragno=-32768
C.2.18.
element 'mysql_readonly' not found in path
C.2.19.
The Primary replicator stopped with a JDBC error.
C.2.20.
trepctl status hangs
C.2.21.
Error: could not settle on encryption_client algorithm
C.2.22.
ERROR backup.BackupTask Backup operation failed: null
C.2.23.
Backup/Restore is not bringing my host back to normal
C.2.24.
Replicator fails to connect after updating password
C.2.25.
There were issues configuring the sandbox MySQL server
C.2.26.
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.27.
Starting replication after performing a restore because of an invalid restart sequence number
C.2.28.
Triggers not firing correctly on Replica
C.2.29.
WARN [KeepAliveTimerTask] - Error while sending a KEEP_ALIVE query to connection.
C.2.30.
Connector shows errors with "java.net.SocketException: Broken pipe"
C.2.31.
ERROR >> host1 >> can't alloc thread
C.2.32.
ERROR 1010 (HY000) at line 5094506: Error dropping database (can't rmdir './mysql-bin/', errno: 17)
C.2.33.
ERROR 1580 (HY000) at line 5093787: You cannot 'DROP' a log table if logging is enabled
C.2.34.
Event application failed: seqno=20725782 fragno=0 message=java.sql.SQLDataException: Data too long for column 'eventid' at row 1