I had an interesting situation to deal with this morning. The server that runs our production version of MySQL crashed with some type of kernel error (Win2K). When the server was brought back up, MySQL which runs as a service was not running when I checked on it this morning. I could not restart the service so I opened a command prompt and issued:
mysqld --console This instance aborted saying that the InnoDB logfile size in the .cnf file did not match the actual logfile size on disk, which was zero. I have a single database defined that is MyISAM and don't use InnoDB at all at this point. I deleted all of the files that matched the pattern 'ib_logfile' from the mysql\data directory and successfully restarted the service. This begs a few questions: 1. Is there a way to configure the server to just support MyISAM databases, i.e. disabling the support for InnoDB? My though is that this would prevent the same error from happening again. 2. I have more or less a default installation and do not use a .cnf file for settings. I could not locate a .cnf file on the server other than the examples in the mysql root directory, i.e. my-huge, my-large, my-medium, and my-small. Why did the MySQL server complain about the logfile size from a .cnf file? Should I be using a .cnf file and where should it be located? I have but a single, small database with only two tables. Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters USA Central Time Zone 636-922-9158 ext. 8652 fax 636-447-4471 [EMAIL PROTECTED] www.nisc.cc -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
