MySQL 5.7 Release Notes
On Windows, mysqld uses the
--log-error,
--pid-file, and
--console options to determine
whether mysqld writes the error log to the
console or a file, and, if to a file, the file name:
If
--consoleis given, mysqld writes the error log to the console. (--consoletakes precedence over--log-errorif both are given, and the following items regarding--log-errordo not apply. Prior to MySQL 5.7, this is reversed:--log-errortakes precedence over--console.)If
--log-erroris not given, or is given without naming a file, mysqld writes the error log to a file namedhost_name.err--pid-fileoption is specified. In that case, the file name is the PID file base name with a suffix of.errin the data directory.If
--log-erroris given to name a file, mysqld writes the error log to that file (with an.errsuffix added if the name has no suffix). The file ___location is under the data directory unless an absolute path name is given to specify a different ___location.
If the server writes the error log to the console, it sets the
log_error system variable to
stderr. Otherwise, the server writes the
error log to a file and sets
log_error to the file name.
In addition, the server by default writes events and error messages to the Windows Event Log within the Application log:
Entries marked as
Error,Warning, andNoteare written to the Event Log, but not messages such as information statements from individual storage engines.Event Log entries have a source of
MySQL.Information written to the Event Log is controlled using the
log_syslogsystem variable, which on Windows is enabled by default. See Section 5.4.2.3, “Error Logging to the System Log”.