MySQL Forums
Forum List  »  Install & Repo

Re: Unsupported redo log format
Posted by: Jack Waterhouse
Date: February 24, 2020 12:43PM

I did that - thanks. I have 5.6 installed.

Now I'm getting:

2020-02-24 13:39:04 9260 [Note] InnoDB: Completed initialization of buffer pool
2020-02-24 13:39:04 9260 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2020-02-24 13:39:04 9260 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2020-02-24 13:39:04 9260 [ERROR] Plugin 'InnoDB' init function returned error.
2020-02-24 13:39:04 9260 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-02-24 13:39:04 9260 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-02-24 13:39:04 9260 [ERROR] Aborting

I've seen this one before, and it's always proven fixable by adding

innodb_data_file_path = ibdata1:18M:autoextend

in /etc/my.cnf .

This isn't working now - I'm not entirely certain mysqld is even looking at /etc/my.cnf , as nothing I do with that file appears to affect it.

Once again, any help you can offer will be greatly appreciated.

-Jack

Options: ReplyQuote


Subject
Written By
Posted
February 23, 2020 02:21PM
Re: Unsupported redo log format
February 24, 2020 12:43PM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.