David; Thanks, it did work. I thought it might--just wanted to be sure that deleting the logfile or editing the .cnf file wouldn't make things worse somehow.
And thanks too for the gentle direction to the manual; I have been digging around for the last several hours, but mostly under the 'Windows' sections. Now that I'm once again a man of leisure, I'll try to commit the relevant sections to mind. Perhaps there should be a handy abbreviation: RTRPOTFM, for Read The Right Part Of TFM.... :-) Huge relief to have this working again: I can't thank you enough for the quick response. Best, --Chris -----Original Message----- From: Logan, David (SST - Adelaide) [mailto:[EMAIL PROTECTED] Sent: Thursday, October 14, 2004 6:54 PM To: Christopher J. Mackie; [EMAIL PROTECTED] Subject: RE: MySQL 4.1.5 upgrade going badly--mysqld won't start Hi Chris, The appropriate sections of the my.cnf (or my.ini on windows) file to edit are # # Set the innodb engine parameters # innodb_data_home_dir = /u01/app/dmc/db/dmcpdb innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /u01/app/dmc/db/dmcpdb innodb_log_arch_dir = /u01/app/dmc/db/dmcpdb innodb_buffer_pool_size = 32M innodb_additional_mem_pool_size = 20M innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 As you can see, the log file size is probably not the same as you had in the previous my.cnf. Your previous my.cnf must have been overwritten along with all the appropriate parameters. To get past the error message you are seeing, either change the innodb_log_file_size parameter or delete the log file and let innodb create it itself. All of this is described in the manual in chapter 16, the paragraph you need is probably 16.4 HTH and you get things going soon. Regards David Logan Database Administrator HP Managed Services 148 Frome Street, Adelaide 5000 Australia +61 8 8408 4273 - Work +61 417 268 665 - Mobile +61 8 8408 4259 - Fax -----Original Message----- From: Christopher J. Mackie [mailto:[EMAIL PROTECTED] Sent: Friday, 15 October 2004 8:11 AM To: [EMAIL PROTECTED] Subject: MySQL 4.1.5 upgrade going badly--mysqld won't start I'm on a Win32 server, but I'm hoping from the error log contents that the question isn't Windows-specific. I'm having a Very Bad Day trying to upgrade a MySQL server from 4.0.18 to 4.1.5. After several problems resolved, I'm almost there--got the new engine to recognize the old dbs, etc. But now, after what I thought would be an ordinary removal/reinstall of the daemon (most of the problems related to the new daemon picking up defaults from an install into another location), the Win service won't start. Here's the relevant section of the error log: InnoDB: Error: log file .\ib_logfile0 is of different size 0 19922944 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 041014 18:20:37 [ERROR] Can't init databases 041014 18:20:37 [ERROR] Aborting 041014 18:20:37 [NOTE] MySQL: Shutdown complete (Trying to start the service from Windows gives Error 1037) Can I edit the cnf file? Clear the InnoDB logfile? I'm getting pretty desperate--site's been down a long time. Any help much appreciated. --Chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
