MySQL Server has several logs that can help you find out what activity is taking place.
|Log Type||Information Written to Log|
|Error log||Problems encountered starting, running, or stopping mysqld|
|General query log||Established client connections and statements received from clients|
|Binary log||Statements that change data (also used for replication)|
|Relay log||Data changes received from a replication master server|
|Slow query log||Queries that took more than
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
statement; execute mysqladmin with a
argument; or execute mysqldump with a
--master-data option. See
Section 188.8.131.52, “FLUSH Syntax”, Section 4.5.2, “mysqladmin — Client for Administering a MySQL Server”, and
Section 4.5.4, “mysqldump — A Database Backup Program”. In addition, the binary log is flushed
when its size reaches the value of the
max_binlog_size system variable.
You can control the general query and slow query logs during runtime. You can enable or disable logging, or change the log file name. You can tell the server to write general query and slow query entries to log tables, log files, or both. For details, see Section 5.2.1, “Selecting General Query and Slow Query Log Output Destinations”, Section 5.2.3, “The General Query Log”, and Section 5.2.5, “The Slow Query Log”.
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 184.108.40.206, “The Slave Relay Log”.
For information about log maintenance operations such as expiration of old log files, see Section 5.2.6, “Server Log Maintenance”.
For information about keeping logs secure, see Section 220.127.116.11, “Passwords and Logging”.