[MDEV-30030] Upgrading problems from MariaDb 10.10.1 to 10.10.2 Created: 2022-11-18  Updated: 2022-11-25  Resolved: 2022-11-18

Status: Closed
Project: MariaDB Server
Component/s: Upgrades
Affects Version/s: 10.10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Oli Sennhauser Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: upgrade
Environment:

Linux Ubuntu 20.04, na

Attachments: File chef_mariadb-1010_error.log    

 Description   

We have downloaded the recent MariaDB 10.10.2 version for some testings and tried to upgrade from 10.10.1 to 10.10.2. The upgrade miserably failed:

mariadb-upgrade --user=root --force
 
Error: Server version (10.10.1-MariaDB-log) does not match with the version of
 
the server (10.10.2-MariaDB) with which this program was built/distributed. You can
 
use --skip-version-check to skip this check.
 
FATAL ERROR: Upgrade failed

then

mariadb-upgrade --user=root --force --skip-version-check
 
ERROR 1728 (HY000) at line 837: Cannot load from mysql.proc. The table is probably corrupted

and

mariadb-upgrade --user=root
 
This installation of MariaDB is already upgraded to 10.10.1-MariaDB.
 
There is no need to run mysql_upgrade again for 10.10.2-MariaDB.
 
You can use --force if you still want to run mysql_upgrade



 Comments   
Comment by Elena Stepanova [ 2022-11-18 ]

This message would normally be issued if the mariadb-upgrade binary that you are running is from 10.10.2, but mariadbd it connects to is still 10.10.1. Can you verify that it's not the case?
Maybe the server package didn't upgrade on some reason, or the binary didn't get replaced, or the server did not get restarted after the upgrade.

Comment by Oli Sennhauser [ 2022-11-18 ]

Hi Elena

Your argument about not restarting the server seems quite valid. Also the original error message, when I read it again, says the same.
I cannot reproduce it any more now because I restarted the daemon and re-initialized the database.

So makes sense to close this issue.

Sorry for bothering you!

Comment by Elena Stepanova [ 2022-11-18 ]

oli,

Thanks for the confirmation. If you still have the syslog from the time of upgrade, maybe we could try to understand why the server wasn't restarted. Assuming it's a deb package installation, the restart is supposed to happen automatically, so it's somewhat worrisome if it didn't.

Comment by Oli Sennhauser [ 2022-11-18 ]

Hello Elena

That is easy to explain: It was a Layer-8 error which caused the not-starting of the mariadbd!
It is NOT a DEB package but a binary tarball. In combination with Layer-8 problems this is disastrous!
But I will attach the error log anyway...

Comment by Elena Stepanova [ 2022-11-18 ]

Thanks, I see.
Indeed, there is no indication of any attempt, failed or not, to shut down in the error log at the time when upgrade occurred, so apparently some integration is missing.

Generated at Thu Feb 08 10:13:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.