Bug #57789 | mysql server can not start,nothing in error log! | ||
---|---|---|---|
Submitted: | 28 Oct 2010 3:00 | Modified: | 29 Oct 2010 7:55 |
Reporter: | Jayson f | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Options | Severity: | S3 (Non-critical) |
Version: | 5.1.51 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[28 Oct 2010 3:00]
Jayson f
[28 Oct 2010 4:06]
Jayson f
This too evidence bug,if a dogmatic bug fixer set this "not bug",i will shit MYSQL everyday after.
[28 Oct 2010 11:05]
MySQL Verification Team
error box
Attachment: error_message.png (image/png, text), 64.72 KiB.
[28 Oct 2010 11:06]
MySQL Verification Team
See prior attached picture.
[29 Oct 2010 7:26]
Jayson f
Yes,look for my old windows Application log,i found it.thanks, but that is windows function.that is not MYSQL error log. handbook No.5.2.2 say: "On Windows, error output is always written to the host_name.err",but fail in doing. Some one do this wrong,doubt again.
[29 Oct 2010 7:55]
Jayson f
As your point,some one write "skip_name_resolve = ON" or "skip-name-resolve = ON" in linux my.cnf again, do not log "option '--skip-name-resolve' cannot take an argument" in linux MYSQL errror.log, write that in /var/log/messages is good. "Wrong do nothing change, but also all sophistry" is mysql bug fixer.