Bug #77977 Error log file disabled if mysqld is started as a windows service
Submitted: 7 Aug 2015 10:20 Modified: 11 Aug 2015 15:52
Reporter: Jon Olav Hauglid Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Logging Severity:S2 (Serious)
Version:5.7.8 OS:Windows
Assigned to: CPU Architecture:Any

[7 Aug 2015 10:20] Jon Olav Hauglid
Description:
As reported in a comment here:
http://mysqlserverteam.com/the-mysql-5-7-8-release-candidate-is-available/

5.7.8 contains a regression where the error log file is disabled when
mysqld is started as a Windows service (error log info is still available
in the event log).

How to repeat:
Start mysqld as a service on Windows
+
SELECT @@log_error;

Notice that the result is 'stderr' and not the error log file specified by
the configuration file.
[9 Aug 2015 16:28] MySQL Verification Team
http://bugs.mysql.com/bug.php?id=77998 is a duplicate
[11 Aug 2015 15:52] Paul DuBois
Noted in 5.7.9, 5.8.0 changelogs.

On Windows, if the MySQL server was started as a service, logging to
the error log file was disabled.
[29 Sep 2015 17:08] Dominique Ottello
Hi,

Why ?
Remove the log file is a complete regression.
This unnecessarily clutters Windows events with a whole bunch of information that have nothing to do there.
Replace the log file, even if mysql is launched as a service, as it was before.
[1 Oct 2015 14:13] Dominique Ottello
Hello,
While this is considered closed, I wish to continue to make comments.
Nobody answered my question: Why?

Search MySQL errors to a text file only dedicated to MySQL is extremely more simple and easy as looking into the mysteries of the "Event Viewer" of Windows that it includes thousands and thousands of entries that apply to the system and all associated software.

Delete this opportunity to have a simple text file is not - in any way - progress. This is a great restriction in the possibility of improving the use of MySQL.
Before taking this decision, did you see how simply been errors are written in the "Event Viewer"? And as it is "easy" to find an error that applies only to MySQL?
I sincerely hope that you cancel this regression.
[2 Oct 2015 7:28] Ståle Deraas
Posted by developer:
 
Hi Dominique,

5.7.8 introduced this bug, and this is now fixed in 5.7.9, which will be released shortly.