Latest batch of updates fails - Error: systemd conflicts with initscripts-9.49.17-1.el7.x86_64

Virtualmin
1

I have a new batch of 17 updates, CENTOS 7, and they are all failing with the same error, see attached for complete listing…

Now updating cyrus-sasl ..

Installing package(s) with command /bin/yum -y install cyrus-sasl ..
 
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.ventraip.net.au
 * epel: fedora.uberglobalmirror.com
 * extras: mirror.ventraip.net.au
 * updates: mirror.ventraip.net.au
Resolving Dependencies
--> Running transaction check
---> Package cyrus-sasl.x86_64 0:2.1.26-17.el7 will be updated
---> Package cyrus-sasl.x86_64 0:2.1.26-19.2.el7 will be an update
--> Processing Dependency: cyrus-sasl-lib(x86-64) = 2.1.26-19.2.el7 for package: cyrus-sasl-2.1.26-19.2.el7.x86_64
--> Processing Dependency: systemd >= 219 for package: cyrus-sasl-2.1.26-19.2.el7.x86_64
--> Running transaction check
---> Package cyrus-sasl-lib.x86_64 0:2.1.26-17.el7 will be updated
--> Processing Dependency: cyrus-sasl-lib(x86-64) = 2.1.26-17.el7 for package: cyrus-sasl-md5-2.1.26-17.el7.x86_64
--> Processing Dependency: cyrus-sasl-lib(x86-64) = 2.1.26-17.el7 for package: cyrus-sasl-gssapi-2.1.26-17.el7.x86_64
--> Processing Dependency: cyrus-sasl-lib(x86-64) = 2.1.26-17.el7 for package: cyrus-sasl-plain-2.1.26-17.el7.x86_64
---> Package cyrus-sasl-lib.x86_64 0:2.1.26-19.2.el7 will be an update
---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated
--> Processing Dependency: systemd = 208-20.el7_1.6 for package: systemd-sysv-208-20.el7_1.6.x86_64
--> Processing Dependency: systemd = 208-20.el7_1.6 for package: systemd-python-208-20.el7_1.6.x86_64
---> Package systemd.x86_64 0:219-19.el7 will be an update
--> Processing Dependency: systemd-libs = 219-19.el7 for package: systemd-219-19.el7.x86_64
--> Running transaction check
---> Package cyrus-sasl-gssapi.x86_64 0:2.1.26-17.el7 will be updated
---> Package cyrus-sasl-gssapi.x86_64 0:2.1.26-19.2.el7 will be an update
---> Package cyrus-sasl-md5.x86_64 0:2.1.26-17.el7 will be updated
---> Package cyrus-sasl-md5.x86_64 0:2.1.26-19.2.el7 will be an update
---> Package cyrus-sasl-plain.x86_64 0:2.1.26-17.el7 will be updated
---> Package cyrus-sasl-plain.x86_64 0:2.1.26-19.2.el7 will be an update
---> Package systemd-libs.x86_64 0:208-20.el7_1.6 will be updated
---> Package systemd-libs.x86_64 0:219-19.el7 will be an update
---> Package systemd-python.x86_64 0:208-20.el7_1.6 will be updated
---> Package systemd-python.x86_64 0:219-19.el7 will be an update
---> Package systemd-sysv.x86_64 0:208-20.el7_1.6 will be updated
---> Package systemd-sysv.x86_64 0:219-19.el7 will be an update
--> Processing Conflict: systemd-219-19.el7.x86_64 conflicts initscripts < 9.49.28-1
--> Processing Conflict: systemd-219-19.el7.x86_64 conflicts dracut < 033-243
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package dracut.x86_64 0:033-241.el7_1.5 will be updated
---> Package dracut.x86_64 0:033-360.el7_2 will be an update
---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated
---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated
--> Processing Conflict: systemd-219-19.el7.x86_64 conflicts initscripts < 9.49.28-1
--> Finished Dependency Resolution
Error: systemd conflicts with initscripts-9.49.17-1.el7.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

.. install failed!

Does anyone have any advice whether I should try to use the suggested options, or is there another fix?

2

Howdy,

Hmm, the issue seems to be certain package versions conflicting with other packages that are installed.

In particular, it seems RPM thinks that initscripts and dracut are too old for the version of systemd it’s trying to install.

You may want to try manually updating initscripts and/or dracut, just to see what it says.

It’s possible something unusual is going on, which may show up when updating them.

If you have some third party packages installed, it’s possible those are playing a role in the issue.

-Eric

3

https://www.centos.org/forums/viewtopic.php?f=48&t=55472

4

Yeah, that’s me!

5

This was resolved by my host.