Description:
Hello,
I tried to log an error by activating some error logging via MySQL Administrator. I could
not yet trace the bug, but I did found a lot of other bugs :>
See the error loggings below
1) 080722 14:07:45 [Warning] No argument was provided to --log-bin, and --log-bin-index
was not used; so replication may break when this MySQL server acts as a master and has
his hostname changed!! Please use '--log-bin=MAIN-bin' to avoid this problem.
080722 14:07:48 InnoDB: Started; log sequence number 267 2988792131
C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: File '.\MAIN-bin.000028' not found
(Errcode: 2)
080722 14:07:48 [ERROR] Failed to open log (file '.\MAIN-bin.000028', errno 2)
080722 14:07:48 [ERROR] Could not open log file
080722 14:07:48 [ERROR] Can't init tc log
080722 14:07:48 [ERROR] Aborting
2) 080722 14:00:42 [ERROR] The update log is no longer supported by MySQL in version 5.0
and above. It is replaced by the binary log. Now starting MySQL with --log-bin instead.
080722 14:00:42 [Warning] No argument was provided to --log-bin, and --log-bin-index was
not used; so replication may break when this MySQL server acts as a master and has his
hostname changed!! Please use '--log-bin=MAIN-bin' to avoid this problem.
080722 14:00:45 InnoDB: Started; log sequence number 267 2988792121
C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: File '.\MAIN-bin.000028' not found
(Errcode: 2)
080722 14:00:45 [ERROR] Failed to open log (file '.\MAIN-bin.000028', errno 2)
080722 14:00:45 [ERROR] Could not open log file
080722 14:00:45 [ERROR] Can't init tc log
080722 14:00:45 [ERROR] Aborting
3) when starting the remaning server with remaning traces, it was damn slow and stoped
with a windows treat error. And at the end VBA was wasting its time wating for the
odbc-connection
4) had to do all kind of tricks trying to activate the log more ore less just before the
error is supposed to happen, because tracing the database during the whole proces is just
not doable (100.000 times more logging than OK)
So,
- real problems,
- not up to date administrator gui and
- also inadequate tracing facilitys (IMHO)
Sincerely,
Louis
How to repeat:
Just
1 & 2
- stop the server
- activate e.g. all in the gui posible traces (leaf the file names emty)
- activate the server
- it will stop by itself
- see the error log
3 & 4
- try to debug an error which occur someware in a programm flow, which is executing a few
mln records first and that do something which generate the error. Programm is accessing
mysql via ODBC
