Mysql Server Logs; The Error Log - Oracle 5.0 Reference Manual

If the slave is updating a nontransactional table when it is forcibly killed, the slave's data may
become inconsistent with the master.
5. The server shuts down or closes storage engines.
At this stage, the server flushes the table cache and closes all open tables.
Each storage engine performs any actions necessary for tables that it manages. For example,
MyISAM
(starting from 5.0.5: unless
tablespace, and terminates its own internal threads.
6. The server exits.

5.2. MySQL Server Logs

MySQL Server has several logs that can help you find out what activity is taking place.
Log Type
Error log
General query log
Binary log
Relay log
Slow query log
By default, no logs are enabled (except the error log on Windows). The following log-specific sections
provide information about the server options that enable logging.
By default, the server writes files for all enabled logs in the data directory. You can force the server
to close and reopen the log files (or in some cases switch to a new log file) by flushing the logs. Log
flushing occurs when you issue a
or
refresh
option. See
a MySQL Server", and
the binary log is flushed when its size reaches the value of the
variable.
The relay log is used only on slave replication servers, to hold data changes from the master server
that must also be made on the slave. For discussion of relay log contents and configuration, see
Section 16.2.2.1, "The Slave Relay
For information about log maintenance operations such as expiration of old log files, see
"Server Log
For information about keeping logs secure, see

5.2.1. The Error Log

The error log contains information indicating when
critical errors that occur while the server is running. If
automatically checked or repaired, it writes a message to the error log.
On some operating systems, the error log contains a stack trace if
to determine where
You can specify where
option. If the option is given with no
flushes any pending index writes for a table.
innodb_fast_shutdown
Information Written to Log
Problems encountered starting, running, or stopping
Established client connections and statements received from clients
Statements that change data (also used for replication)
Data changes received from a replication master server
Queries that took more than
execute
FLUSH LOGS
argument; or execute
Section 13.7.6.2, "FLUSH
Section 4.5.4,
Maintenance".
died. See
mysqld
writes the error log with the
mysqld

MySQL Server Logs

InnoDB
statement; execute
with a
mysqldump --flush-logs
Syntax", Section 4.5.2,
"mysqldump — A Database Backup
Log".
Section 6.1.2.3, "Passwords and
mysqld
mysqld
MySQL Internals: Porting to Other
value,
file_name mysqld
543
flushes its buffer pool to disk
[1241] is 2), writes the current LSN to the
[465]
long_query_time
mysqladmin
[300] or
--master-data
"mysqladmin — Client for Administering
Program". In addition,
max_binlog_size
Logging".
was started and stopped and also any
notices a table that needs to be
dies. The trace can be used
mysqld
Systems.
--log-error[=file_name]
uses the name
host_name.err
mysqld
seconds to
with a
flush-logs
[302]
[1472] system
Section 5.2.5,
[411]