[chef] Re: Re: Re: Enabling bin-logging with mysql recipe

[Lamont Granquist < >]

proper procedure to change the innodb_log_file_size is to shut the database down, change the size, remove the old log files (ib_logfile0/ib_logfile1), and then restart the database.  if the log file sizes don't match it won't start back up.

it is a good idea to do this as the default is tiny and you'll reduce both your write i/o and cpu utilization.  as you increase this number startup times will increase, so you probably don't need to push this beyond 256M and you should monitor and actively tune it if you think you need to go higher.

On 12/13/12 10:45 AM, Mathieu Martin wrote:

" type="cite"> Hey Mike,

Yes, chef restarted it properly. I've also tried restarting manually it as well...

Based on further investigation, the problem may have been caused by my setting innodb_log_file_size.

Changing this after a mysql database is initialized has a tendency to cause:

121213 12:31:16 [ERROR] Plugin 'InnoDB' init function returned error.

121213 12:31:16 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE

 failed.

121213 12:31:16 [ERROR] Unknown/unsupported table type: InnoDB

121213 12:31:16 [ERROR] Aborting

I'll try to investigate whether there's a problem in the mysql cookbook with this setting when I get a moment, or if I was doing it wrong.

Anyhow, I've solved my problem for now.

Thanks,

Mat