• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Issue with yum update

xdelios

Basic Pleskian
Hello,

I have Plesk Onyx installed on one of my CentOS 7 servers.
I had previously installed Cloudlinux which then I removed with the guide in CL page.

Time passed and all was good.
Now I am experiencing a weird error on yum update

Code:
Finished Dependency Resolution
Error: Package: rsyslog-8.24.0-12.el7.x86_64 (base)
           Requires: libsystemd.so.0(LIBSYSTEMD_229)(64bit)
           Available: systemd-libs-219-42.el7.x86_64 (base)
               libsystemd.so.0(LIBSYSTEMD_229)(64bit)
           Available: systemd-libs-219-42.el7_4.1.x86_64 (updates)
               libsystemd.so.0(LIBSYSTEMD_229)(64bit)
           Available: systemd-libs-219-42.el7_4.4.x86_64 (updates)
               libsystemd.so.0(LIBSYSTEMD_229)(64bit)
           Installed: 1:systemd-libs-219-30.el7_3.7.cloudlinux.x86_64 (@cloudlinux-x86_64-server-7)
              ~libsystemd.so.0(LIBSYSTEMD_209)(64bit)
              ~libsystemd.so.0(LIBSYSTEMD_211)(64bit)
              ~libsystemd.so.0(LIBSYSTEMD_213)(64bit)
              ~libsystemd.so.0(LIBSYSTEMD_214)(64bit)
              ~libsystemd.so.0(LIBSYSTEMD_216)(64bit)
              ~libsystemd.so.0(LIBSYSTEMD_217)(64bit)
              ~libsystemd.so.0(LIBSYSTEMD_219)(64bit)
 You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
plesk-mysql-server-17.5.3-cos7.build1705170317.16.x86_64 has missing requires of mariadb-server >= ('0', '5.0.60', None)

I tried yum sync in case that could fix it but nothing.
I also tried skip-broken so see if it would work but it did not.

If I understand correctly something from the CL installation is still in the system and causes the problem.

How can I fix that?

Regards
 
Hello,

I am trying the solution from the thread you linked me to.

Does not seem to work and I get an error at the end
Code:
Skip-broken could not solve problems
Error: Package: 1:systemd-python-219-30.el7_3.7.cloudlinux.x86_64 (@cloudlinux-x86_64-server-7)
           Requires: systemd = 1:219-30.el7_3.7.cloudlinux
           Removing: 1:systemd-219-30.el7_3.7.cloudlinux.x86_64 (@cloudlinux-x86_64-server-7)
               systemd = 1:219-30.el7_3.7.cloudlinux
           Downgraded By: systemd-219-42.el7_4.4.x86_64 (updates)
               systemd = 219-42.el7_4.4
           Available: systemd-219-42.el7.x86_64 (base)
               systemd = 219-42.el7
           Available: systemd-219-42.el7_4.1.x86_64 (updates)
               systemd = 219-42.el7_4.1
Error: Package: 1:systemd-python-219-30.el7_3.7.cloudlinux.x86_64 (@cloudlinux-x86_64-server-7)
           Requires: systemd-libs = 1:219-30.el7_3.7.cloudlinux
           Removing: 1:systemd-libs-219-30.el7_3.7.cloudlinux.x86_64 (@cloudlinux-x86_64-server-7)
               systemd-libs = 1:219-30.el7_3.7.cloudlinux
           Downgraded By: systemd-libs-219-42.el7_4.4.x86_64 (updates)
               systemd-libs = 219-42.el7_4.4
           Available: systemd-libs-219-42.el7.i686 (base)
               systemd-libs = 219-42.el7
           Available: systemd-libs-219-42.el7_4.1.i686 (updates)
               systemd-libs = 219-42.el7_4.1
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
plesk-mysql-server-17.5.3-cos7.build1705170317.16.x86_64 has missing requires of mariadb-server >= ('0', '5.0.60', None)
[root@shared01 ~]# rpm -qa 'systemd*' 'libgudev*'
systemd-sysv-219-30.el7_3.7.cloudlinux.x86_64
libgudev1-219-30.el7_3.7.cloudlinux.x86_64
systemd-libs-219-30.el7_3.7.cloudlinux.x86_64
systemd-219-30.el7_3.7.cloudlinux.x86_64
systemd-python-219-30.el7_3.7.cloudlinux.x86_64
 
Actually, it is not Plesk related issue, but OS packages dependences/upgrade issue. Therefore I will move this thread to Open Topics
Obviously that you need to remove all cloudlinux orphaned packages and it requires fine work with the rpm utility directly on your server. Not sure that this can be resolved in scope of forum discussions. Only common recommendations may be provided here, but you must do all the delicate work yourself or hire an experienced administrator.
 
Back
Top