Author Topic: MariaDB error preventing other updates  (Read 119 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
MariaDB error preventing other updates
« on: March 26, 2025, 10:01:46 PM »
I apologize as I know there are many entries regarding MariaDB updates. I just have a quick question. I am running CWPpro version: 0.9.8.1201 on AlmaLinux 8. CWP yum manager is showing only 1 update which is MariaDB. I know that I have to manually update MariaDB 10.4 to 10.11 manually. However, the error is causing the other updates to not show up. On a test box, I remarked out all lines in the /etc/yum.repos.d/mariadb.repo, I refreshed, then all kinds of other updates showed up and I was able to successfully complete those.

Is it advisable to do this just to get other updates applied before I upgrade MariaDB? Or is there a better best/practice way of getting the needed updates completed?
-------------------------------------------------------------------------------------------------------------------------------------------------
Last metadata expiration check: 0:14:54 ago on Tue Mar 25 12:24:17 2025.
Dependencies resolved.
================================================================================
 Package               Architecture  Version               Repository      Size
================================================================================
Upgrading:
 MariaDB-server        x86_64        10.11.11-1.el8        mariadb         28 M

Transaction Summary
================================================================================
Upgrade  1 Package

Total download size: 28 M
Downloading Packages:
MariaDB-server-10.11.11-1.el8.x86_64.rpm        3.8 MB/s |  28 MB     00:07   
--------------------------------------------------------------------------------
Total                                           3.8 MB/s |  28 MB     00:07     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1
  Running scriptlet: MariaDB-server-10.11.11-1.el8.x86_64                   1/1
  Running scriptlet: MariaDB-server-10.11.11-1.el8.x86_64                   1/2

******************************************************************
A MySQL or MariaDB server package (MariaDB-server-10.4.34-1.el8.x86_64) is installed.

Upgrading directly from MySQL 10.4 to MariaDB 10.11 may not
be safe in all cases.  A manual dump and restore using mysqldump is
recommended.  It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.

A manual upgrade is required.

- Ensure that you have a complete, working backup of your data and my.cnf
  files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages.  Usually this command will
  list the packages you should remove:
  rpm -qa | grep -i '^mysql-'

  You may choose to use 'rpm --nodeps -ev ' to remove
  the package which contains the mysqlclient shared library.  The
  library will be reinstalled by the MariaDB-shared package.
- Install the new MariaDB packages supplied by MariaDB Foundation
- Ensure that the MariaDB server is started
- Run the 'mysql_upgrade' program

This is a brief description of the upgrade process.  Important details
can be found in the MariaDB manual, in the Upgrading section.
******************************************************************
error: %prein(MariaDB-server-10.11.11-1.el8.x86_64) scriptlet failed, exit status 1

  Verifying        : MariaDB-server-10.11.11-1.el8.x86_64                   1/2
  Verifying        : MariaDB-server-10.4.34-1.el8.x86_64                    2/2

Failed:
  MariaDB-server-10.4.34-1.el8.x86_64    MariaDB-server-10.11.11-1.el8.x86_64   

Offline
*****

Offline
*
Re: MariaDB error preventing other updates
« Reply #2 on: March 27, 2025, 05:34:44 PM »
I understand that. I wondering about getting the other updates applied before I start upgrading all of my servers.

Offline
*****
Re: MariaDB error preventing other updates
« Reply #3 on: March 27, 2025, 06:49:14 PM »
Change your mariadb.repo back to 10.4.

Just changing it to 10.11 won't work anyways using dnf.

Or do the manual update like @overseer posted, then run the rest of the AL8 updates.