- B.5.2 Common Errors When Using MySQL Programs
- B.5.2.1 Access denied
- B.5.2.2 Can't connect to [local] MySQL server
- B.5.2.3 Lost connection to MySQL server
- B.5.2.4 Client does not support authentication protocol
- B.5.2.5 Password Fails When Entered Interactively
- B.5.2.6 Host 'host_name' is blocked
- B.5.2.7 Too many connections
- B.5.2.8 Out of memory
- B.5.2.9 MySQL server has gone away
- B.5.2.10 Packet too large
- B.5.2.11 Communication Errors and Aborted Connections
- B.5.2.12 The table is full
- B.5.2.13 Can't create/write to file
- B.5.2.14 Commands out of sync
- B.5.2.15 Ignoring user
- B.5.2.16 Table 'tbl_name' doesn't exist
- B.5.2.17 Can't initialize character set
- B.5.2.18 'File' Not Found and Similar Errors
- B.5.2.19 Table-Corruption Issues
If you have started mysqld with
--myisam-recover, MySQL
automatically checks and tries to repair
MyISAM tables if they are marked as 'not
closed properly' or 'crashed'. If this happens, MySQL writes
an entry in the hostname.err file
'Warning: Checking table ...' which is
followed by Warning: Repairing table if the
table needs to be repaired. If you get a lot of these errors,
without mysqld having died unexpectedly
just before, then something is wrong and needs to be
investigated further.
As of MySQL 5.5.3, when the server detects
MyISAM table corruption, it writes
additional information to the error log, such as the name and
line number of the source file, and the list of threads
accessing the table. Example: Got an error from
thread_id=1, mi_dynrec.c:368. This is useful
information to include in bug reports.
See also Section 5.1.2, “Server Command Options”, and Section 22.5.1.7, “Making a Test Case If You Experience Table Corruption”.
User Comments
Add your own comment.