Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.5.4
-
None
-
Ubuntu 20.04 / Linux 5.4.0
Description
After an upgrade from 10.4 to 10.5 (following the instructions on https://mariadb.com/kb/en/upgrading-from-mariadb-104-to-mariadb-105/), MariaDB fails to start:
2020-07-09 19:43:43 0 [Note] InnoDB: Using Linux native AIO
|
2020-07-09 19:43:43 0 [Note] InnoDB: Uses event mutexes
|
2020-07-09 19:43:43 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
|
2020-07-09 19:43:43 0 [Note] InnoDB: Number of pools: 1
|
2020-07-09 19:43:43 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
|
2020-07-09 19:43:43 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
|
2020-07-09 19:43:43 0 [Note] InnoDB: Initializing buffer pool, total size = 107374182400, chunk size = 134217728
|
2020-07-09 19:43:46 0 [Note] InnoDB: Completed initialization of buffer pool
|
2020-07-09 19:43:46 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
|
2020-07-09 19:43:46 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.13.
|
2020-07-09 19:43:46 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
|
2020-07-09 19:43:46 0 [Note] InnoDB: Starting shutdown...
|
2020-07-09 19:43:49 0 [ERROR] Plugin 'InnoDB' init function returned error.
|
2020-07-09 19:43:49 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
|
2020-07-09 19:43:49 0 [Note] Plugin 'FEEDBACK' is disabled.
|
2020-07-09 19:43:49 0 [ERROR] Failed to initialize plugins.
|
2020-07-09 19:43:49 0 [ERROR] Aborting
|
Output from sudo journalctl -u mariadb.service indicates a problem with max_open_files, but this seems to be just a warning:
Starting MariaDB 10.5.4 database server...
|
Jul 09 19:43:43 nose mariadbd[1527643]: 2020-07-09 19:43:43 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.4-MariaDB-1:10.5.4+maria~bionic-log) starting as process 1527643 ...
|
Jul 09 19:43:43 nose mariadbd[1527643]: 2020-07-09 19:43:43 0 [Warning] Could not increase number of max_open_files to more than 16364 (request: 66099)
|
Jul 09 19:43:49 nose systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
|
Jul 09 19:43:49 nose systemd[1]: mariadb.service: Failed with result 'exit-code'.
|
Jul 09 19:43:49 nose systemd[1]: Failed to start MariaDB 10.5.4 database server.
|
Downgrading to 10.4 works.
InnoDB config:
innodb-defragment = 1
|
innodb-flush-method = O_DIRECT
|
innodb-log-file-size = 10G
|
innodb-log-buffer-size = 256M
|
innodb-read-io-threads = 16
|
innodb-write-io-threads = 16
|
innodb-flush-log-at-trx-commit = 2
|
innodb-flush-neighbors = 0
|
innodb-file-per-table = 1
|
innodb-buffer-pool-size = 100G
|
innodb-compression-algorithm = zlib
|
How can get further insight into the problem with InnoDB initialization?
Attachments
Issue Links
- is part of
-
MDEV-27530 InnoDB - Performance issues after upgrade 10.4.22 to 10.5.13
- Closed
- relates to
-
MDEV-26932 upgrade wizard never finishes at Phase 9/10 and hit "InnoDB: Upgrade after a crash is not supported" after restart
- Closed
-
MDEV-12353 Efficient InnoDB redo log record format
- Closed