Oracle 5.0 Reference Manual page 2846

This prints out where
create a bug report and include the output from the preceding command with the bug report.
However, in most cases it does not help us to have just a stack trace to find the reason for the
problem. To be able to locate the bug or provide a workaround, in most cases we need to know the
statement that killed
Section 1.7, "How to Report Bugs or
21.3.1.6. Using Server Logs to Find Causes of Errors in
Note that before starting
with myisamchk. See
If dies or hangs, you should start
mysqld
Section 5.2.2, "The General Query
file for the query that killed mysqld.
If you use the default general query log file, the log is stored in the database directory as
host_name.log
should verify this by restarting
tools. If this works, you should also test all complicated queries that didn't complete.
You can also try the command
that
mysqld
You can find the queries that take a long time to execute by starting
enabled. See
If you find the text
probably have found a query that causes
tables with
myisamchk
MySQL log files to see whether one fails. If you find such a query, try first upgrading to the newest
MySQL version. If this doesn't help and you can't find anything in the
report the bug to a MySQL mailing list. The mailing lists are described at http://lists.mysql.com/, which
also has links to online list archives.
If you have started
repair
MyISAM
writes an entry in the
by
Warning: Repairing table
without
mysqld
investigated further. See
It is not a good sign if
Checking table...
21.3.1.7. Making a Test Case If You Experience Table Corruption
If you get corrupted tables or if
whether this bug is reproducible by doing the following:
• Take down the MySQL daemon (with
• Make a backup of the tables (to guard against the very unlikely case that the repair does something
bad).
• Check all tables with
-r database/table.MYI.
• Make a second backup of the tables.
Debugging a MySQL Server
died. If that does not help you find out why
mysqld
and preferably a test case so that we can repeat the problem! See
mysqld
with the general query log enabled, you should check all your tables
mysqld
Chapter 5, MySQL Server
Log". When
In most cases it is the last query in the log file that killed mysqld, but if possible you
mysqld
EXPLAIN
is using indexes properly. See
Section 5.2.4, "The Slow Query
mysqld restarted
(see Chapter 5, MySQL Server
with
mysqld --myisam-recover
tables if they are marked as 'not closed properly' or 'crashed'. If this happens, MySQL
hostname.err
having died unexpectedly just before, then something is wrong and needs to be
Section 5.1.3, "Server Command
did die unexpectedly, but in this case, you should not investigate the
mysqld
messages, but instead try to find out why
mysqld
myisamchk -s
Problems".
Administration.
with the general query log enabled. See
mysqld
dies again, you can examine the end of the log
mysqld
and executing the found query from the
on all statements that takes a long time to ensure
SELECT
Section 13.8.2,
Log".
in the error log file (normally named hostname.err) you
to fail. If this happens, you should check all your
mysqld
Administration), and test the queries in the
[415], MySQL automatically checks and tries to
file
'Warning: Checking table ...'
if the table needs to be repaired. If you get a lot of these errors,
always fails after some update commands, you can test
mysqladmin shutdown).
database/*.MYI. Repair any wrong tables with
2826
mysqld
mysqld
mysql
"EXPLAIN Syntax".
with the slow query log
mysqld
mail archive, you should
mysql
Options".
died.
mysqld
died, you should
command-line
which is followed
myisamchk