7.5 upgrade: systemd.i686 requires liblz4.so.1

General support questions
Maurits
Posts: 2
Joined: 2018/05/15 11:00:20

7.5 upgrade: systemd.i686 requires liblz4.so.1

Postby Maurits » 2018/05/15 11:12:15

Hi all,

I have a whole range of virtual servers failing to update to Centos 7.5, because systemd-libs won't update (taking with it a whole lot of dependencies after I upgrade the rest with --skip-broken). They are currently at release 7.4.1708 and kept up to date with yum daily until this problem started to occur.

Problem is, systemd-libs.x86_64 would update fine but systemd-libs.i686 complains that liblz4.so.1 is missing. Indeed the only liblz4 I have is x86_64 and resides in /usr/lib64/. Apparently there is no 32-bit version anywhere in the Centos repository. I don't know why this wasn't a problem before, or why I even have a full set of 32-bit systemd tools and related stuff on my system.

Trying to only update systemd-libs.x86_64 obviously gives a "multilib problem".

Can I just get rid of the 32 bit systemd-libs and all dependencies? Is it normal that 64-bit servers have a full set of 32 bit systemd libs and similar tools installed? (My servers are pretty much based on ISPConfig's "perfect server setup" for Centos 7, nothing exotic going on). Or is this a bug in the repositories?

User avatar
avij
Forum Moderator
Posts: 2451
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: 7.5 upgrade: systemd.i686 requires liblz4.so.1

Postby avij » 2018/05/15 11:35:01

There is lz4-1.7.5-2.el7.i686.rpm in the repository, I don't know what is the problem. Perhaps seeing the full yum update output would help.

In any case, unless you have a specific need for some 32bit package, you can yum remove '*.i686'. Perhaps the 32bit packages got pulled in when you upgraded to 7.4.1708 (see release notes and search for rdma).

User avatar
TrevorH
Forum Moderator
Posts: 22590
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: 7.5 upgrade: systemd.i686 requires liblz4.so.1

Postby TrevorH » 2018/05/15 11:41:16

Did you exclude *i686 packages in yum.conf or the .repo files?
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

Maurits
Posts: 2
Joined: 2018/05/15 11:00:20

Re: 7.5 upgrade: systemd.i686 requires liblz4.so.1

Postby Maurits » 2018/05/16 15:08:36

Well if there is a 32 bit lz4, yum persistently refuses to install (or find) it even when asked directly, although I have no exclusion for i686 anywhere.

But yes, the only dependency on the 32-bit systemd was rdma, which in turn pulled in a whole lot of other dependencies. So many that I thought they were necessary for some reason. :) But I'm reassured by the mentioned issue in 7.4.1708, so thanks for that. Removing them on the least critical of my vservers did the trick and seems to do no harm, so the rest will follow.

So I'll never know why the 32-bit lz4 keeps eluding me, but fortunately I don't need it. :) Thanks everyone!

User avatar
TrevorH
Forum Moderator
Posts: 22590
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: 7.5 upgrade: systemd.i686 requires liblz4.so.1

Postby TrevorH » 2018/05/16 15:16:47

Someone else just had this problem and it turned out that they had EPEL installed and had given it a "priority=10" in the .repo file but had not assigned any priorities to anything else which meant that all other repos, including base and updates, were given priority=99. That meant that EPEL was more important than base/updates so the lz4 packages in EPEL were preferred over the new ones in base/updates.

Solution: add priority=1 to both [base] and [updates] in CentOS-Base.repo and maybe to [extras] too.
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

ITI
Posts: 21
Joined: 2014/02/26 20:19:38
Location: Canada
Contact:

Re: 7.5 upgrade: systemd.i686 requires liblz4.so.1

Postby ITI » 2018/05/16 23:47:07

I had same issue on 2 of my servers while a 3rd updated just fine.

After adding priority=1 to all sections in Centos-base.repo they updated just fine.
When I check the 3rd servers repos it turns out that the epel.rep had priority=10 commented out in the [epel] section. Hmm!

That said, the right solution or easier solution maybe to just comment out any priority settings in the epel.repo

Update: Very Slow reboot
The other problem I was experiencing and have been trying to resolve was with these 2 servers taking for ever to reboot, 8 to 12 minutes.
After correcting the priority issue and completing the yum updates, they now both reboot in under a minute.
What a pleasant surprise.
I do remember reading something some where that suggested the liblz4 affected booting.
I think it's safe to say that it does/did.
Glen