MySQL Bugs: #33863: Unable to start server

Bug #33863	Unable to start server
Submitted:	14 Jan 2008 13:57	Modified:	8 Jun 2008 7:53
Reporter:	Bill Gehling	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	MySQL Server 5.0 v45	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
I have attempted many times to download a complete new server from scratch. In each case the installation and configuration work fine but the server fails to start. The error file shows the server shutting down normally during the first run  at 0:17:44. Next at 0:17:45 InnoDB finds a the file .ibdata1 missing, so it creates it. Then just 1 second later (at 0:17:46) the server aborts the server because it fails to find InnoDB. I would be happy if there was some way of repairing the system, but I cannot find anything in the documentation or the web that would help.

How to repeat:
I have repeated this many times using all possible combinations using the wizard and using the command line. I have installed with only the default options, and also tried other options, but still the same result - the server fails to load.

Suggested fix:
Some documentation of InnoDB, how it works, and what can be safely changed, would help very much

Thank you for a problem report. Please, send your complete error log, my.ini file and the results of:

dir data

from the directory where you installed MySQL.

I suspect this problem arises because of the fact that InnoDB and MySQL are developed by different teams, and that during intallation neither program is fully aware of the nature of the problem and able to coordinate recovery. This seems that this condition could occur to anyone, particularly someone new to the product. It should be covered by notes in the documentation, more helpful error messages, and possibly a tool to recover from the condition.

the error log file

Attachment: bill-r3000.err (application/octet-stream, text), 197.49 KiB.

Directory of the data folder

Attachment: dirdata.txt (text/plain), 668 bytes.

my.ini on the MySQL Server 5.0 folder

Attachment: my.ini (application/octet-stream, text), 9.03 KiB.

Thank you for the feedback. If you don't have data could you please delete
all files in your data directory which begin with ib*:

14/01/2008  12:17 AM        10,485,760 ibdata1
14/01/2008  10:12 PM        10,485,760 ib_logfile0
14/01/2008  12:13 AM        10,485,760 ib_logfile1

then from a command line try to start the server:

mysqld --standalone --console

and see if the server creates adequately the InnoDB files, otherwise
print here the error messages. Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Bill,

many thanks for writing a bug report.

Please, can you tell us, if the suggested solution from Miguel works.

When it not works, please can you paste error message here?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".