Unable to Upgrade from MariaDB 10.3 to 10.5

Sujoy Dhar

• November 06, 2022 08:34

Hi, Recently I tried to upgrade from MariaDB 10.3 to MariaDB 10.5 but it Failed and thrown the below error message, Can you please help me in this ? [QUOTE]The system was not able to ensure the availability of the "MariaDB-client" package: The package "MariaDB-client" with version "10.5" is not available via yum: Loaded plugins: fastestmirror, rhnplugin, universal-hooks, versionlock This system is receiving updates from CLN. Determining fastest mirrors * EA4: 184.94.196.94 * cpanel-addons-production-feed: 184.94.196.94 * cpanel-plugins: 184.94.196.94 * cloudlinux-x86_64-server-7: az1-clmirror.a2hosting.com * elrepo: dfw.mirror.rackspace.com * epel: irltoolkit.mm.fcix.net Excluding 6 updates due to versionlock (use "yum versionlock status" to show them) Installed Packages MariaDB-client.x86_64 10.3.25-1.el7.centos @MariaDB103 Obtained version information from system. Proceeding with MySQL/MariaDB upgrade despite the following: Critical: In MariaDB 10.4 and later, the mysql.global_priv table has replaced the mysql.user table. The mysql.user table is converted into a view of the mysql.global_priv table during the database upgrade. The dedicated mariadb.sys user is created as the definer of the new mysql.user view. Critical: The "mytop" package is not compatible due to MDEV-22552. If "mytop" is installed, the upgrade process will uninstall the "mytop" package. Normal: All binaries previously beginning with `mysql` now begin with `mariadb`. Symlinks are created for the corresponding mysql commands to ensure backwards compatibility. Usually that should not cause any changed behavior, but when starting the MariaDB server via systemd, or via the `mysqld_safe` script symlink, the server process will now always be started as `mariadbd`, not`mysqld`. Any 3rd party software or scripts looking for the `mysqld` name in the system process list must now look for `mariadbd` instead.

• 

  Sujoy Dhar

  • November 06, 2022 17:21

  I have followed this :

  1
• 

  andrew.n

  • November 07, 2022 14:43

  @cPRex for visibility here. How did you try to upgrade it exactly? from WHM or via command line?

  0
• 

  cPRex Jurassic Moderator

  • November 07, 2022 15:29

  After checking the ticket, it looks like the client had some additional MySQL tools that were not compatible with the update. These were Galera and mytop. After removing those, the update worked well and the client confirmed things were working normally.

  0
• 

  Sujoy Dhar

  • November 08, 2022 07:13

  So let me complete this : Before upgrading make sure you do run the below command first : [QUOTE]mv /usr/local/bin/mytop{,.Disabled}
  [QUOTE]yum remove galera
  Check is the versionlock is clear or not ? [QUOTE]# yum versionlock list ... 0:MariaDB-server-10.3.36-1.el7.centos.* 0:MariaDB-shared-10.3.36-1.el7.centos.* 0:MariaDB-devel-10.3.36-1.el7.centos.* 0:MariaDB-common-10.3.36-1.el7.centos.* 0:MariaDB-compat-10.3.36-1.el7.centos.* 0:MariaDB-client-10.3.36-1.el7.centos.* versionlock status done
  In my case it was lock and Full database was Down so unable to understand what could be done . Then another Support " Donell Cox " run the below command : [QUOTE]yum versionlock clear
  Then the Database server gone up and I have Resumed the upgrade and it worked.

  0
• 

  kodeslogic

  • November 08, 2022 12:04

  @Sujoy Dhar Thank you for sharing the details with the community.

  0

Please sign in to leave a comment.