'MYSQL 8.0 - unsupported redo log format

I have recently updated mysql that was located under my xampp folder, and i've got the following errors, reporting from the log file :

2018-04-19T12:59:19.667059Z 0 [System] [MY-010116] [Server] C:\xampp\mysql\bin\mysqld.exe (mysqld 8.0.11) starting as process 9324
2018-04-19T12:59:20.025280Z 1 [ERROR] [MY-013090] [InnoDB] InnoDB: Unsupported redo log format (0). The redo log was created before MySQL 5.7.9
2018-04-19T12:59:20.026140Z 1 [ERROR] [MY-012930] [InnoDB] InnoDB: Plugin initialization aborted with error Generic error.
2018-04-19T12:59:20.229069Z 1 [ERROR] [MY-011013] [Server] Failed to initialize DD Storage Engine.
2018-04-19T12:59:20.230803Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2018-04-19T12:59:20.231371Z 0 [ERROR] [MY-010119] [Server] Aborting
2018-04-19T12:59:20.233136Z 0 [System] [MY-010910] [Server] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete (mysqld 8.0.11)  MySQL Community Server - GPL.

I have been told if updating your mysql, you should comment out the deprecated configs that are located in your my.ini, but i had no idea what to comment out, so i left it as it is.

Any idea what causes this?



Solution 1:[1]

Mac OS X Users

The ib_logfiles are here

rm /usr/local/var/mysql/ib_logfile*

Solution 2:[2]

Docker users

I faced with the same error while using dockerized mariaDB.

The solution was:

remove the docker image:

docker image ls
docker rmi imagename

remove the volume:

docker volume ls
docker volume rm yourvolume

remove the container:

docker ps -a
docker rm yourcontainer

Then:

docker-compose up

Windows 10 Users

Also in windows if you want to remove the log files as it was suggested earlier: The ib_logfiles are in

C:\ProgramData\MySQL\MySQL Server x.x\Data

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Tenzin Chemi
Solution 2