Bug #26847 Cannot view log files
Submitted: 5 Mar 2007 19:53 Modified: 18 Feb 2009 14:52
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.2.10 OS:Windows (XP Pro)
Assigned to: Mike Lischke CPU Architecture:Any

[5 Mar 2007 19:53] [ name withheld ] 
Description:
All tabs (Error, Slow, General) of the Server Logs section are empty on all instances. The buttons are also blanked out or disabled. I have 3 instances running, 4.0, 4.1 & 5.0, all writing files to different directories. Kind of a pain to have to open the files in notepad! This has been as issue since early 1.2.x but I thought someone else would have found it by now ;-)

How to repeat:
Open Administrator...Server Logs
[5 Mar 2007 20:29] Valeriy Kravchuk 
Thank you for a bug report. Verified just as described.
[9 Mar 2007 14:57] Michael G. Zinner 
Hi,

have you explicitly enabled the log files on the Startup Variables section? MA tries to find the log files based on the entries there.

Thanks,
Mike
[9 Mar 2007 16:26] [ name withheld ] 
No it doesn't. I enable for 2 instances and don't for one. Regardless if I enable and specify a name or not, {computername}.err is generated for each instance. I should at least be able to view those....cannot. All logs are in {install dir}/data/
[16 Mar 2007 15:13] Valeriy Kravchuk 
Please, restart instances after enabling logs and check again. It works for me, at least, for Slow Query Log.
[16 Mar 2007 15:55] [ name withheld ] 
True, I finally got the all of the tabs to work after specifying files for all (error, slow, query) and restarting multiple times. It seems to not notice them initially (the files were created on restart). There may be a slight display bug when you initially click the tab button after restart. It also seems that since there is a default file created for logging, the Administrator should know that and be able to see those log files *without* specifying a log file name in the setup. That's how the older versions worked. Thanks!
[24 Mar 2007 3:28] Valeriy Kravchuk 
Error log should be acessible immediately. Thus, this is still a verified bug.
[30 Oct 2007 21:20] Nancy Anderson 
I can not get any log files to show regardless of setting file names. If the "Open Other File" was not disabled could I point to the file in question manually? As opposed to MySQL Admin trying to find the log files automatically?
[18 Feb 2009 14:52] Mike Lischke 
Fixed in repository administrator, revision 407