Bug #2854 Slow Log and General Log panes blank
Submitted: 17 Feb 2004 23:07 Modified: 11 Mar 2004 8:30
Reporter: Jonathan Foo Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.0.1a ALPHA OS:Windows (Windows XP Home)
Assigned to: Michael G. Zinner CPU Architecture:Any

[17 Feb 2004 23:07] Jonathan Foo
Description:
The contents of my error log display in the Error Logs tab of the Server Logs section, but the Slow Log and General Log tabs both display empty windows.  I've examined both of those files in a text editor; they do contain log entries.

The "Search", "Save Log Page", and "Refresh" buttons at the bottom of both of these tabs are grayed out.

How to repeat:
Click either the Slow Log or General Log tabs under the Server Logs section; both display no data.
[18 Feb 2004 7:53] Michael G. Zinner
Thanks for reporting.

Could you post the filenames of your log files and where they are located on your system?
[19 Feb 2004 12:55] Jonathan Foo
In an attempt to cut down on my own confusion, I keep my logfiles located outside the data/ directory.  Administrator allows my to use either absolute or relative paths, so I've had both of the following set in Administrator:

c:/mysql/logs/error_logfile.txt
c:/mysql/logs/slow_queries_logfile.txt
c:/mysql/logs/query_logfile.txt

and

../logs/error_logfile.txt
../logs/slow_queries_logfile.txt
../logs/query_logfile.txt

Using each path specification, I first stopped the server, then deleted any existing logfiles, then restarted the server, and the logfiles popped back into existence as expected.  As mentioned, the contents of the error_logfile.txt do display in administrator, but the slow_queries_logfile.txt and the queries_logfile.txt do not.
[23 Feb 2004 18:03] Jonathan Foo
Correction to the above - when I specify an absolute path to my error log (c:/mysql/logs/error_logfile.txt) in the "Startup Variables"... "Log files" section, the file does pop into existence upon server restart if it hadn't already existed in that location.  

However, after I restart the service, the error log pane in Administrator grays out, like the Slow and General log panes.  Shutting down and restarting Administrator does not un-gray the log panes, nor does stopping and restarting the mysql service.  I've tried both *nix- and Windows-style directory separators ("c:\mysql\logs\error_logfile.txt" and "c:/mysql/logs/error_logfile.txt").

To get the error log pane to activate, I need to go back to relative path specifications (both "../logs/error_logfile.txt" and "..\logs\error_logfile.txt" work), and restart the service.  The error log pane is now active again.

The Slow and General logs panes remain grayed out regardless of path specification.

mysqld-max-nt.exe
mysql 4.1.1a
[11 Mar 2004 8:30] Michael G. Zinner
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html