perfSONAR User Q&A and Other Discussion

["David J. Chaffin" <>]

That kind of message is usually yum being confused by simultaneous install and update.

Usually better to update first, then install, as Mark says.

Also "yum check" can find multiple installed versions that will mess things up.

Current is -26.el7

# rpm -qa | grep openssl | grep 1.0.2k

openssl-devel-1.0.2k-26.el7_9.x86_64

openssl-libs-1.0.2k-26.el7_9.x86_64

openssl-1.0.2k-26.el7_9.x86_64

# rpm -qa | grep perfsonar-test

perfsonar-testpoint-4.4.6-1.el7.noarch

#

--

David

---

From: <> on behalf of Jarett <>
Sent: Thursday, March 30, 2023 1:27 PM
To: Mark Feit <>; <>
Subject: RE: [perfsonar-user] Openssl library conflict with CentOS 7.9

 

Hm. But apt seems to think that the package specifically requires -19 (= rather than >=)? Am I reading this incorrectly?

 

From:
Sent: Thursday, March 30, 2023 10:44 AM
To: ;
Subject: Re: [perfsonar-user] Openssl library conflict with CentOS 7.9

 

Jarett DeAngelis writes:

 

When trying to install `perfsonar-testpoint`, I get this:

 

--> Finished Dependency Resolution

Error: Package: 1:openssl-1.0.2k-19.el7.x86_64 (base)

           Requires: openssl-libs(x86-64) = 1:1.0.2k-19.el7

           Installed: 1:openssl-libs-1.0.2k-25.el7_9.x86_64 (@updates)

               openssl-libs(x86-64) = 1:1.0.2k-25.el7_9

           Available: 1:openssl-libs-1.0.2k-19.el7.x86_64 (base)

               openssl-libs(x86-64) = 1:1.0.2k-19.el7

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

 

—skip-broken does this over again and installs nothing. You can’t remove the -25 revision of openssl because everything depends on it. How do we get around this issue?

 

I’m not seeing that on a fresh install of the production or staging (beta) code and an install of just openssl on a bare EL7 machine works just fine.  In all three instances, 1:openssl-1.0.2k-26.el7_9 and the same version of openssl-libs are installed.

 

Your system appears to have a variety of versions installed or available, which makes me wonder if there’s a combination of mirrors involved where one that got used wasn’t up to date.  A ‘yum clean all’ followed by a ‘yum update’ to bring everything up to current and then installing the testpoint might work.

 

My take on situations like that is that the system got itself into a weird state and should be nuked from orbit because it’s the only way to be sure.  :-)

 

--Mark