Percona Server Update Failure from 8.0.22-13 to 8.0.36-28

MySQL & MariaDB Percona Server for MySQL 8.0
1

I’m encountering an error after upgrading Percona Server from version 8.0.22-13 (previously upgraded from Percona 5.7) to version 8.0.36-28. Here’s the relevant log snippet:

2024-03-16T10:18:09.213203Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36-28) starting as process 991142
2024-03-16T10:18:09.228330Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-03-16T10:18:10.574382Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 8.0.22-13, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
2024-03-16T10:18:10.574402Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2024-03-16T10:18:11.477838Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2024-03-16T10:18:11.477965Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-03-16T10:18:11.477986Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-03-16T10:18:11.478358Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.36-28)  Percona Server (GPL), Release '28', Revision '47601f19'$. 

dpkg: error processing package percona-server-server (--configure):
 installed percona-server-server package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of percona-server-test:
 percona-server-test depends on percona-server-server (= 8.0.36-28-1.focal); however:
  Package percona-server-server is not configured yet.

dpkg: error processing package percona-server-test (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of percona-server-dbg:
 percona-server-dbg depends on percona-server-server (= 8.0.36-28-1.focal); however:
  Package percona-server-server is not configured yet.

dpkg: error processing package percona-server-dbg (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of percona-server-rocksdb:
 percona-server-rocksdb depends on percona-server-server (= 8.0.36-28-1.focal); however:
  Package percona-server-server is not configured yet.

dpkg: error processing package percona-server-rocksdb (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.31-0ubuntu9.14) ...
Errors were encountered while processing:
 percona-server-server
 percona-server-test
 percona-server-dbg
 percona-server-rocksdb
E: Sub-process /usr/bin/dpkg returned an error code (1)

The error message indicates an issue with upgrading InnoDB due to innodb_fast_shutdown = 2 being set during a previous shutdown of the older version (8.0.22-13).
I’ve reviewed the upgrade documentation at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html but haven’t found a specific solution for this scenario.

I’m seeking assistance from the community to resolve this issue. Any suggestions or insights would be greatly appreciated!

Here are some additional details that might be helpful:

Operating System: Ubuntu 20.04
Upgrade Method: apt

Thank you for your time and support!

2

There were major changes related to redo log in v 8.0.30.
You should do a shutdown with innodb_fast_shutdown=0 and then trigger the upgrade.
This will allow full purge and is the best for upgrades.

your dpkg command seems to be having dependency problems.
How are you trying to upgrade? Can you mention the command?

3

Percona had been updated via apt, and to address issues with missing package installations, I resolved them with apt --fix-broken install . The database issues were related to a MySQL crash. I managed to recover forcing InnoDB recovery by setting innodb_force_recovery to 5, placing InnoDB in read-only mode…
Fortunately, this allowed me to perform dumps, test them for data consistency, and load them onto a new server.

4

It’s good to hear that the package issues were fixed.

Any value greater than 3 for innodb_force_recovery can cause the data loss.
The crash seems to be with the value innodb_fast_shutdown = 2.
You should always shutdown your database with innodb_fast_shutdown = 0 when upgrading.

Good to hear