Bug #4009 Erratic behavior with page flipper for server logs
Submitted: 4 Jun 2004 15:16 Modified: 21 Jun 2004 14:32
Reporter: Bob Dankert Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.0.4 BETA OS:Windows (XP SP2)
Assigned to: Michael G. Zinner CPU Architecture:Any

[4 Jun 2004 15:16] Bob Dankert
Description:
Connected to the localhost mysql server, when I first bring up the server logs the logs are blank, showing "0/1" pages, and the page flipper has the first 9 sections dark blue, last section light blue.  If I click on the page flipper, the first page of the error log pops up, but it now says "Events of page 4294967294/1".  If I click the page flipper again, it goes to show "1/1".  Also, after clicking this, after I hover over the left and right buttons just to the right of the page flipper, they become disabled.  If I switch to the Slow Log tab and then double click on the page flipper, all of the logs go blank and all of the log controls go disabled, as though it were not connected to the localhost.

Please let me know if you need anymore details with this.

How to repeat:
Follow steps above
[4 Jun 2004 15:38] Michael G. Zinner
Thanks for reporting! Could you upload your error log file here? I am not able to reproduce it with the error log files on my machines.
[4 Jun 2004 15:41] Bob Dankert
Absolutely.  Now for the big question, which file is this specifically?
[4 Jun 2004 16:32] Michael G. Zinner
Please check in the MySQL Administrator Startup Variables section on the Log files tabsheet if you have set a different directory or name for the Error Logfile Name.

If this variable is not set, it should be in your servers data directory and named <machinename>.err

For me that is in C:\Program Files\MySQL\data and it is named mikework.err
[4 Jun 2004 16:35] Bob Dankert
Two files uploaded.  Please let me know if you need anything else.
[5 Jun 2004 0:29] Michael G. Zinner
Strange. I still cannot reproduce the bug. Could you try to open one of the files you sent with the [Open other File] button and see if the behaviour persists?

If this works the file the bug must be located in the file detection mechanism.
[15 Jun 2004 16:10] Bob Dankert
I've since formatted my computer, I downloaded 1.0.5 today and this did not have the same problem.  This could be because I did a new database install, a new windows install (still xp sp2), new admin install, or the new admin version.  I will let you know if I am able to reproduce it in the future.

Thanks