Ubuntu
mysql-8.0 package

  1. Bug #2029262
  2. Comment #2

Comment 2 for bug 2029262

Revision history for this message
Athos Ribeiro (athos-ribeiro) wrote :

These are the relevant snippets from the attached logs:

Setting up mysql-server-8.0 (8.0.33-0ubuntu0.22.04.4) ...
Specified filename /var/lib/mysql/ibdata1 does not exist.
...
[ERROR] [MY-010946] [Server] Failed to start mysqld daemon. Check mysqld error log.

And in the mysql log, we see:

[System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33-0ubuntu0.20.04.4) starting as process 1569
[ERROR] [MY-011011] [Server] Failed to find valid data directory.
[ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
[ERROR] [MY-010119] [Server] Aborting
[System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.33-0ubuntu0.20.04.4) (Ubuntu).
[System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33-0ubuntu0.22.04.4) starting as process 65221
[ERROR] [MY-011011] [Server] Failed to find valid data directory.
[ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
[ERROR] [MY-010119] [Server] Aborting
[System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.33-0ubuntu0.22.04.4) (Ubuntu).

which shows that the service was already failing to start for the 20.04 package.

Finally, the old config file has an entry:

datadir = /var/lib/jenkins/mysql

while the new config file has no such entry.

From the data above, I suppose your initial mysql installation used /var/lib/jenkins/mysql and mysql was never set to run using the default datadir.

Since updating the data in the datadir is part of the mysql upgrade process, you should not accept replacing your configuration files with the default ones during the package upgrade process, since you do have a custom mysql setup.

To upgrade the package, you should instead ensure your configuration file is compatible with the new mysql version.

Since this seems to be a configuration issue rather than a bug in the package, I am marking this bug as incomplete for now. If you disagree with the assessment, please state the reasons you believe this is indeed a bug with the mysql package and set the status of this bug back to new.