Leap Almalinux 8 to 9

E

ericosman

Verified User
Joined
Nov 25, 2019
Messages
660
Location
Weert
Hi all,

I would like to update my Almalinux 8 to Almalinux 9, but i get the following reasons i cant upgrade yet:

Code: 
Risk Factor: high (error)
Title: DNF execution failed with non zero exit code.
Summary: {"STDOUT": "Extra Packages for Enterprise Linux 9 - x86_64   23 MB/s |  20 MB     00:00    \n", "STDERR": "warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.\nNo matches found for the following disable plugin patterns: subscription-manager\nRepository appstream is listed more than once in the configuration\nRepository appstream-debuginfo is listed more than once in the configuration\nRepository appstream-source is listed more than once in the configuration\nRepository baseos is listed more than once in the configuration\nRepository baseos-debuginfo is listed more than once in the configuration\nRepository baseos-source is listed more than once in the configuration\nRepository extras is listed more than once in the configuration\nRepository extras-debuginfo is listed more than once in the configuration\nRepository extras-source is listed more than once in the configuration\nwarning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.\nWarning: Package marked by Leapp to upgrade not found in repositories metadata: gpg-pubkey leapp leapp-upgrade-el8toel9 python3-leapp\nTransaction check: \n\n Problem 1: package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1()(64bit), but none of the providers can be installed\n  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed\n  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.2)(64bit), but none of the providers can be installed\n  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.4)(64bit), but none of the providers can be installed\n  - liburing-1.0.7-3.el8.x86_64 from @System  does not belong to a distupgrade repository\n  - problem with installed package MariaDB-server-11.4.7-1.el8.x86_64\n Problem 2: cannot install the best update candidate for package liburing-1.0.7-3.el8.x86_64\n  - cannot install both liburing-2.5-1.el9.x86_64 from almalinux9-appstream and liburing-1.0.7-3.el8.x86_64 from @System\n  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1()(64bit), but none of the providers can be installed\n  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed\n  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.2)(64bit), but none of the providers can be installed\n  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.4)(64bit), but none of the providers can be installed\n  - package MariaDB-server-compat-11.4.4-1.el8.noarch from @System requires MariaDB-server >= 11.0.0, but none of the providers can be installed\n  - problem with installed package MariaDB-server-compat-11.4.4-1.el8.noarch\n", "hint": "If there was a problem reaching remote content (see stderr output) and proxy is configured in the YUM/DNF configuration file, the proxy configuration is likely causing this error. Make sure the proxy is properly configured in /etc/dnf/dnf.conf. It's also possible the proxy settings in the DNF configuration file are incompatible with the target system. A compatible configuration can be placed in /etc/leapp/files/dnf.conf which, if present, it will be used during some parts of the upgrade instead of original /etc/dnf/dnf.conf. In such case the configuration will also be applied to the target system. Note that /etc/dnf/dnf.conf needs to be still configured correctly for your current system to pass the early phases of the upgrade process."}
Key: 1e26c8b86cec72c25c04ca045d2b0ed3e8ca2df5
----------------------------------------
Risk Factor: high
Title: Detected customized configuration for dynamic linker.
Summary: Custom configurations to the dynamic linker could potentially impact the upgrade in a negative way. The custom configuration includes modifications to /etc/ld.so.conf, custom or modified drop in config files in the /etc/ld.so.conf.d directory and additional entries in the LD_LIBRARY_PATH or LD_PRELOAD variables. These modifications configure the dynamic linker to use different libraries that might not be provided by Red Hat products or might not be present during the whole upgrade process. The following custom configurations were detected by leapp:
- The /etc/ld.so.conf file has unexpected contents:
    - /lib64
Remediation: [hint] Remove or revert the custom dynamic linker configurations and apply the changes using the ldconfig command. In case of possible active software collections we suggest disabling them persistently.
Key: cc9bd972af70b7a27f66a37b11a00dcfcb73b1bc
----------------------------------------
Risk Factor: high
Title: Detected custom leapp actors or files.
Summary: We have detected installed custom actors or files on the system. These can be provided e.g. by third party vendors, Red Hat consultants, or can be created by users to customize the upgrade (e.g. to migrate custom applications). This is allowed and appreciated. However Red Hat is not responsible for any issues caused by these custom leapp actors. Note that upgrade tooling is under agile development which could require more frequent update of custom actors.
The list of custom leapp actors and files:
    - /usr/share/leapp-repository/repositories/system_upgrade/common/files/distro/almalinux/rpm-gpg/9/RPM-GPG-KEY-AlmaLinux-9
    - /usr/share/leapp-repository/repositories/system_upgrade/common/files/rpm-gpg/9/RPM-GPG-KEY-AlmaLinux-9
Related links:
    - Customizing your Red Hat Enterprise Linux in-place upgrade: https://red.ht/customize-rhel-upgrade
Remediation: [hint] In case of any issues connected to custom or third party actors, contact vendor of such actors. Also we suggest to ensure the installed custom leapp actors are up to date, compatible with the installed packages.
Key: 2064870018370ce2bde3f977cf753ed8c59848d0
----------------------------------------


So it seems that Maria DB is blocking my upgrade at this moment? How did you guys fix this?
 
zEitEr said:
Hello,

Try:

Bash: 
perl -pi -e 's/^exclude=/#exclude=/' /etc/yum.conf
Click to expand...
Hi,

Tried,

But after still the same error(s)

Code: 
[root@srv1 ~]# cat /etc/yum.conf
[main]
gpgcheck=1
installonly_limit=3
clean_requirements_on_remove=True
best=True
skip_if_unavailable=False
#exclude=*ftpd MariaDB-server* apache* bind-chroot* dovecot* exim* httpd* mariadb-server* mod_* mysql-community-server* mysql-server* nginx* php* sendmail*
 
the error is not readable, so well-formatted will it be as the following:

Code: 
Summary: {"STDOUT": "Extra Packages for Enterprise Linux 9 - x86_64   23 MB/s |  20 MB     00:00
", "STDERR": "warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.
No matches found for the following disable plugin patterns: subscription-manager
Repository appstream is listed more than once in the configuration
Repository appstream-debuginfo is listed more than once in the configuration
Repository appstream-source is listed more than once in the configuration
Repository baseos is listed more than once in the configuration
Repository baseos-debuginfo is listed more than once in the configuration
Repository baseos-source is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Repository extras-debuginfo is listed more than once in the configuration
Repository extras-source is listed more than once in the configuration
warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.
Warning: Package marked by Leapp to upgrade not found in repositories metadata: gpg-pubkey leapp leapp-upgrade-el8toel9 python3-leapp
Transaction check:

 Problem 1: package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1()(64bit), but none of the providers can be installed
  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed
  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.2)(64bit), but none of the providers can be installed
  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.4)(64bit), but none of the providers can be installed
  - liburing-1.0.7-3.el8.x86_64 from @System  does not belong to a distupgrade repository
  - problem with installed package MariaDB-server-11.4.7-1.el8.x86_64
 Problem 2: cannot install the best update candidate for package liburing-1.0.7-3.el8.x86_64
  - cannot install both liburing-2.5-1.el9.x86_64 from almalinux9-appstream and liburing-1.0.7-3.el8.x86_64 from @System
  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1()(64bit), but none of the providers can be installed
  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed
  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.2)(64bit), but none of the providers can be installed
  - package MariaDB-server-11.4.7-1.el8.x86_64 from @System requires liburing.so.1(LIBURING_0.4)(64bit), but none of the providers can be installed
  - package MariaDB-server-compat-11.4.4-1.el8.noarch from @System requires MariaDB-server >= 11.0.0, but none of the providers can be installed
  - problem with installed package MariaDB-server-compat-11.4.4-1.el8.noarch
", "hint": "If there was a problem reaching remote content (see stderr output) and proxy is configured in the YUM/DNF configuration file, the proxy configuration is likely causing this error. Make sure the proxy is properly configured in /etc/dnf/dnf.conf. It's also possible the proxy settings in the DNF configuration file are incompatible with the target system. A compatible configuration can be placed in /etc/leapp/files/dnf.conf which, if present, it will be used during some parts of the upgrade instead of original /etc/dnf/dnf.conf. In such case the configuration will also be applied to the target system. Note that /etc/dnf/dnf.conf needs to be still configured correctly for your current system to pass the early phases of the upgrade process."}

as a possible solution then you might try:

1. add a correct repository from MariaDB site for AlmaLinux 8x or 9x (you will need to check whether or not they offer it)
2. completely remove MariaDB from the server for time of the upgrade and then install it again

and make sure you don't run DirectAdmin legacy. Correct me if I am wrong, but DA legacy does not support MariaDB 11.x
 
You must log in or register to reply here.
Back
Top