(mysql.info.gz) Error log

 
 5.9.1 The Error Log
 -------------------
 
 The error log file contains information indicating when `mysqld' was
 started and stopped and also any critical errors that occur while the
 server is running.
 
 If `mysqld' dies unexpectedly and `mysqld_safe' needs to restart it,
 `mysqld_safe' will write a `restarted mysqld' message to the error log.
 If `mysqld' notices a table that needs to be automatically checked or
 repaired, it writes a message to the error log.
 
 On some operating systems, the error log will contain a stack trace if
 `mysqld' dies. The trace can be used to determine where `mysqld' died.
  Using stack trace.
 
 Beginning with MySQL 4.0.10, you can specify where `mysqld' stores the
 error log file with the `--log-error[=FILE_NAME]' option. If no
 FILE_NAME value is given, `mysqld' uses the name `HOST_NAME.err' and
 writes the file in the data directory.  (Prior to MySQL 4.0.10, the
 Windows error log name is `mysql.err'.)  If you execute `FLUSH LOGS',
 the error log is renamed with a suffix of `-old' and `mysqld' creates a
 new empty log file.
 
 In older MySQL versions on Unix, error log handling was done by
 `mysqld_safe' which redirected the error file to `HOST_NAME.err'.  You
 could change this filename by specifying a `--err-log=FILE_NAME' option
 to `mysqld_safe'.
 
 If you don't specify `--log-error', or (on Windows) if you use the
 `--console' option, errors are written to stderr, the standard error
 output. Usually this is your terminal.
 
 On Windows, error output is always written to the `.err' file if
 `--console' is not given.
Info Catalog
(mysql.info.gz) Log Files
(mysql.info.gz) Query log
automatically generated byinfo2html