MySQL Bugs: #6171: error log not found

Bug #6171	error log not found
Submitted:	20 Oct 2004 8:24	Modified:	14 Dec 2004 2:21
Reporter:	Andreas Götz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.0.13	OS:	Windows (WinXP SP1)
Assigned to:		CPU Architecture:	Any

Description:
When opening the error log page in MA, nothing is shown, log is empty.
My error log is in d:\mysql\data\mysql.err as used by the server. When manually opening the file, contents are displayed. 

How to repeat:
.

Suggested fix:
Enable MA to automatically open this error log file.

I tested on XP and the log error contents is displayed.

mhmm. can still repeat. Mysql&MA are installed in c:\program files\mysql, data folder is d:\mysql\data and the error file is in that folder. it is not displayed when opening ma.
my.ini is in c:\win

more investigation: filemon revealed that MA is looking for fsc76t5476881.err (which is the machinename.err file)- this one exists, but is empty and not updated recently.
mysql.err is currently being updated by the server, but not picked up by MA?

Not sure why this bug was closed as Can't repeat- didn't receive an update to my last comment- could you reopen?

Please verify if your case isn't related to bug:

http://bugs.mysql.com/bug.php?id=6179
MySQL server creates 2 error log files

if yes then isn't MA issue.

Thanks in advance.

Miguel,

thanks for following up- yes, quite possibly. In which server release is the bug fixed- I could only then retest?

Thanks,
Andreas

Miguel,

not sure why bug is waiting on feedback- I can only retest when I know which server release I need to retest?!

Thanks,
Andi

MA 1.0.17 Showing log error with server 4.1.8

Attachment: MA-log-error.PNG (image/png, text), 64.12 KiB.

Hi  Andreas,

I am closing this bug report because I can affirm you that the issue
is already fixed on our source tree with server 4.1.8 (next release)
and MA 1.1.17.

I attached a picture to this bug report.