Bug #77958 WB fails to display error log

• Submitted: 6 Aug 2015 10:03
• Modified: 15 Oct 2015 19:46
• Reporter: Johannes Taxacher
• Status: Closed
• Category: MySQL Workbench: Administration
• Severity: S3 (Non-critical)
• Version: 6.3.4
• OS: Any
• CPU Architecture: Any

[6 Aug 2015 10:03] Johannes Taxacher

Description:
Starting with server version 5.7 the error-log file on windows is written to the Windows Eventlog. When connected to such server, Workbench fails to display the error log as it tries to open a nonexistent error log file because the variable (@@log_error), which WB queries to retrieve the error log file, returns the string "stderr" and WB takes this a filename and tries to open it.

How to repeat:
- Install MySQL Server 5.7.8 or higher and Workbench on a Windows machine (default configuration for server)
- start WB and connect to the server instance
- go to the maintenance section and click on "Server Logs"
the error log file viewer will display an error message about not being able to access the file "<DataDir>/stderr"

Suggested fix:
WB should check whether the value retrieved from @@log_error makes up for a valid/existing filename. If not, i'd suggest WB offers a browse-button for the user to pick a file manually.

WB will need the feature to ready/display the err log from the windows eventlog, for the cases where logging to file is disabled. For remote connections this will have some limitations (e.g. remote administration is only available for win<->win connections)

[15 Oct 2015 19:46] Philip Olson

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.5 release, and here's the changelog entry:

On Windows, and when connecting to MySQL Server 5.7.8 or higher, the
Server Logs did not properly display the MySQL error logs, and it instead
referred to a file named "stderr" that could not be found. This is because
the error log is now written to the Windows Event Log.

Thank you for the bug report.