Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start a container for MySQL 8: Log file ./ib_logfile0 size 18882560 is not a multiple of innodb_page_size #868

Closed
woutersamaey opened this issue Jun 17, 2022 · 11 comments

Comments

@woutersamaey
Copy link
Contributor

I am having the strangest error when starting a simple 8.0 container. Using defaults for everything, yet I get the error Log file ./ib_logfile0 size 18882560 is not a multiple of innodb_page_size and MySQL does not start.

I tried different tags. MySQL 5.7 works, but no luck with version 8

Command on Ubuntu 22.04

docker run --rm -e MYSQL_ROOT_PASSWORD=root mysql:8.0-debian

Output

2022-06-17 07:41:58+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.29-1debian10 started.
2022-06-17 07:41:58+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-06-17 07:41:58+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.29-1debian10 started.
2022-06-17 07:41:59+00:00 [Note] [Entrypoint]: Initializing database files
2022-06-17T07:41:59.021006Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.29) initializing of server in progress as process 43
2022-06-17T07:41:59.025989Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-06-17T07:41:59.238804Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-06-17T07:41:59.842369Z 6 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2022-06-17 07:42:02+00:00 [Note] [Entrypoint]: Database files initialized
2022-06-17 07:42:02+00:00 [Note] [Entrypoint]: Starting temporary server
2022-06-17T07:42:02.861461Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 92
2022-06-17T07:42:02.878071Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-06-17T07:42:02.898578Z 1 [ERROR] [MY-012962] [InnoDB] Log file ./ib_logfile0 size 18882560 is not a multiple of innodb_page_size
2022-06-17T07:42:02.898725Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2022-06-17T07:42:03.389636Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2022-06-17T07:42:03.389814Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2022-06-17T07:42:03.389925Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-06-17T07:42:03.389979Z 0 [ERROR] [MY-010946] [Server] Failed to start mysqld daemon. Check mysqld error log.
2022-06-17T07:42:03.390466Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.29)  MySQL Community Server - GPL.
2022-06-17 07:42:03+00:00 [ERROR] [Entrypoint]: Unable to start server.
@X4mp
Copy link

X4mp commented Jun 17, 2022

We experience the exact same issue here with our development setup on Ubuntu 22.04. It works fine with older Ubuntu and Fedora 35.
According to #861 this will be fixed in zfs 2.1.5, but I couldn't find any confirmation for this.
I would be very happy if there is any sort of workaround to get this to work until it is properly fixed.

@woutersamaey
Copy link
Contributor Author

I am using ZFS as well, so sounds like you're onto something.

@X4mp
Copy link

X4mp commented Jun 17, 2022

According to openzfs/zfs#13329 (comment) this was resolved in openzfs/zfs#13338.
If there is any information on when to expect the patch release for zfs I would be very interested.

@X4mp
Copy link

X4mp commented Jun 17, 2022

Seems like the merged fix is already part of 2.1.5-staging (openzfs/zfs#13532)

@marcitqualab
Copy link

marcitqualab commented Jun 18, 2022

Here is my workaround.

@tianon
Copy link
Member

tianon commented Jun 21, 2022

Nice find! Given this is ZFS-related, there's not likely to be anything we could fix in the image to fix it. 😅

At most, maybe there's an issue on the upstream MySQL project for it? (Going to close this in favor of the more appropriate discussions on the ZFS and/or MySQL projects. 👍)

@tianon tianon closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2022
@ThisIsQasim
Copy link

zfs 2.1.5 was released 2 days ago and I can confirm that it indeed fixes this

@woutersamaey
Copy link
Contributor Author

A bit off topic, but how did you upgrade to 2.1.5? I’m on Ubuntu 22.04.

@ThisIsQasim
Copy link

I am not using Ubuntu. Both versions were self compiled for CentOS Stream 9

how did you upgrade to 2.1.5? I’m on Ubuntu 22.04.

@marcitqualab
Copy link

marcitqualab commented Jun 27, 2022

If you are not in a rush just wait for Canonical to add this package in the apt repos.

If you really want to update I guess that you need to do it manually following the docs here

@cafec0ffee
Copy link

cafec0ffee commented Jun 30, 2022

A bit off topic, but how did you upgrade to 2.1.5? I’m on Ubuntu 22.04.

jonathonf's PPA:
add-apt-repository ppa:jonathonf/zfs
apt install zfsutils-linux zfs-dkms

after reboot:
zfs version

zfs-2.1.5-1 22.04.york0
zfs-kmod-2.1.5-1 22.04.york0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants