The docs for 5.1 say that I can set
log_warnings = 2 to capture
Aborted_connects in the error log. This bug report suggests that this was only merged into 5.5 and 6.0 (and maybe 5.2) but not into 5.1.
I tried out all combinations of
set global log_warnings = 2; and
set global log_warnings = 1; followed by login attempts with valid and invalid users and invalid and no passwords results in nothing in the error log.
- Are the docs incorrect or have I made a mistake somewhere?
- Do other types of aborted connections (such as a loss of network during the login or improper permissions for the database) get logged in the error log?
- Do aborted clients get logged in the error log?
Some other things I have checked/done:
log_erroris set to
- That file exists and the
mysqldprocess has it open.
- The last entry in it is from 2012/06/01.
skip-log-warningsis not set in
my.cnfand the process was started with no arguments.
skip_log_warningsdoes not exist in
SHOW GLOBAL VARIABLES LIKE '%skip%'
- The uptime of MySQL is 50 days.
- I ran
FLUSH LOGSjust in case.
- The version string is
Aborted_connectsvalue is increasing by one every time I try an invalid connection attempt.