In the last episode (Apr 12), Andrew Simpson said:
> One server had a problem while creating a backup last week. The routine
> normally takes about 30 seconds, but in this case went on for over 30
> minutes. During this, the application was responding correctly to other
> users. After a reboot, InnoDB has been disabled, which left the data
> inaccessible. The database was restored using the most recent backup,
> but all tables are now using the MyISAM engine.
[...]
> The errors are due to InnoDB being disabled. As far as I can tell, this
> has happened as the InnoDB log file ib_logfile0 is the wrong size. This
> took me to the description for adding and removing log files at:
> http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html
>
> However, something has happened in this case to expand the file
> id_logfile0 and instructions are not given on how to clean it out and
> start again.
[...]
>
> 070403 16:33:55 InnoDB: Starting shutdown...
> 070403 16:33:57 InnoDB: Shutdown completed; log sequence number 0 81792952
> 070403 16:33:57 [Note] C:\www\xampp\mysql\bin\mysqld-nt.exe: Shutdown
> complete
>
> InnoDB: Error: log file C:\www\xampp\mysql\data\ib_logfile0 is of different
> size 0 134217728 bytes
> InnoDB: than specified in the .cnf file 0 67108864 bytes!
Looks like someone edited the my.cnf file and changed the
innodb_log_file_size variable without restarting the server or deleting
the old logfiles. Assuming the server had shut down cleanly, you
should just have to delete the current logfiles and restart mysql. If
the server had crashed, you would probably want to set
innodb_log_file_size back to 128M, start*stop mysqld to flush any
pending transactions, then lower it down to 64M, delete the logfiles,
and start mysql.
--
Dan Nelson
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
