yum update on CentOS complains about "Multilib version problems" of "nss-softokn-freebl" - yum

On last Friday morning, I tried a "yum update" on my CentOS laptop, and it reported this:
Loaded plugins: fastestmirror, langpacks, verify
Loading mirror speeds from cached hostfile
* base: repo1.dal.innoscale.net
* epel: fedora-epel.mirror.lstn.net
* extras: mirror.unl.edu
* nux-dextop: mirror.li.nux.ro
* rpmfusion-free-updates: mirror.us.leaseweb.net
* updates: mirror.spro.net
Resolving Dependencies
--> Running transaction check
---> Package nss-softokn-freebl.i686 0:3.16.2.3-13.el7_1 will be updated
---> Package nss-softokn-freebl.i686 0:3.16.2.3-14.2.el7_2 will be an update
---> Package python-ecdsa.noarch 0:0.11-3.el7.centos will be obsoleted
---> Package python2-ecdsa.noarch 0:0.13-4.el7 will be obsoleting
---> Package tzdata.noarch 0:2016c-1.el7 will be updated
---> Package tzdata.noarch 0:2016d-1.el7 will be an update
---> Package tzdata-java.noarch 0:2016c-1.el7 will be updated
---> Package tzdata-java.noarch 0:2016d-1.el7 will be an update
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for nss-softokn-freebl which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of nss-softokn-freebl of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude nss-softokn-freebl.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of nss-softokn-freebl installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of nss-softokn-freebl installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: nss-softokn-freebl-3.16.2.3-14.2.el7_2.i686 != nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64
I asked about this on #centos, and someone gave me some exploratory advice, but no real solution.

I experienced the very same issue on a Fedora 20 system (run in a docker container) when trying to install i686 development libraries. Reason were two not matching versions for x86_64 and i686, respectively.
Protected multilib versions: nss-softokn-freebl-3.19.1-1.0.fc20.i686 != nss-softokn-freebl-3.19.2-1.0.fc20.x86_64
For me it helped to call
yum distribution-synchronization
That automatically downgraded the x86_64 version. After that
I could install with
yum install nss-softokn-freebl.i686
and
yum list installed | grep nss-softokn-freebl
showed now:
nss-softokn-freebl.i686 3.19.1-1.0.fc20 #updates
nss-softokn-freebl.x86_64 3.19.1-1.0.fc20 #updates
Problem solved.

Related

Install centreon on centos7.9 raspberrypi

How guys, can you help me I have problem with install centreon:
#yum install centreon-base-config-centreon-engine centreon
output
Loading mirror speeds from cached hostfile
base: mirror.vpsnet.com
centos-kernel: mirror.vpsnet.com
extras: mirror.vpsnet.com
updates: centosh9.centos.org
http://yum.centreon.com/standard/3.4/el7/stable/armhfp/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article
https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
One of the configured repositories failed (Centreon Entreprise Linux reposistory contains software to use with Centreon.),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=centreon-stable ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable centreon-stable
or
subscription-manager repos --disable=centreon-stable
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=centreon-stable.skip_if_unavailable=true
failure: repodata/repomd.xml from centreon-stable: [Errno 256] No more mirrors to try.
http://yum.centreon.com/standard/3.4/el7/stable/armhfp/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
What i done is:
ls /etc/yum.repos.d/
nano /etc/yum.repos.d/centreon.repo #enabled=0
Where can i find package for "centreon-base-config-centreon-engine centreon"
The Centreon version 3.4 is not supported anymore.
You should use an newer version.
Latest is the 21.04.
This version comes with a script that does all the install automatically.
It is described in the "Packages" tab of the Centreon download site: https://download.centreon.com/

CentOs 7 cant install mod_wsgi

I am trying to get a server up and running to run python scripts (Django framework) and such by using the mod_wsgi apache module to handle the scripts, however, it's not playing ball and I don't know enough to figure out what's happening or what I'm doing wrong.
I have been unable to come right using the YUM installer. So far, this is the output:
# sudo yum install mod_wsgi
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* EA4: 169.255.59.74
* cpanel-addons-production-feed: 169.255.59.74
* base: mirror.wiru.co.za
* epel: fedora.mirror.ac.za
* extras: mirror.wiru.co.za
* ius: mirrors.ircam.fr
* updates: mirror.wiru.co.za
* webtatic: uk.repo.webtatic.com
Resolving Dependencies
--> Running transaction check
---> Package mod_wsgi.x86_64 0:3.4-12.el7_0 will be installed
--> Processing Dependency: httpd-mmn = 20120211x8664 for package:
mod_wsgi-3.4-12.el7_0.x86_64
--> Finished Dependency Resolution
Error: Package: mod_wsgi-3.4-12.el7_0.x86_64 (base)
Requires: httpd-mmn = 20120211x8664
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
The first thing that jumped out is the dependency httpd which I tried (and failed) to install using yum. After this, I did some research and found out its an issue with cPanel and that apparently it prevents you from using Yum to install Apache modules and everywhere says I am supposed to use the interface but I have no idea how?
My goal is to figure out how I'm 'supposed' to be loading these modules to get around these obstacles and get my server going. Someone, please help!
I am running:
CentOs 7.5
Apache 2.4.34
EasyApache 4
cPanel 7.40
PHP 5.6.38
On a CentOS 7.5 machine, I updated httpd (Apache) using yum to 2.4.6-80.el7.centos.1. Not exactly sure what your situation is with your pre-installed httpd version 2.4.34. Like I said in my comment above, I only trust versions of software available though yum. Your version is above the standard version so you could experience unexpected results.
Updated:
httpd.i686 0:2.4.6-80.el7.centos.1
Dependency Updated:
httpd-devel.i686 0:2.4.6-80.el7.centos.1
httpd-manual.noarch 0:2.4.6-80.el7.centos.1
httpd-tools.i686 0:2.4.6-80.el7.centos.1
mod_ldap.i686 0:2.4.6-80.el7.centos.1
mod_ssl.i686 1:2.4.6-80.el7.centos.1
After upgrading httpd, I added mod_wsgi and it installed without any problems:
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
mod_wsgi i686 3.4-12.el7_0 base 75 k
Transaction Summary
================================================================================
Install 1 Package
Total download size: 75 k
Installed size: 187 k
Is this ok [y/d/N]: y
Downloading packages:
mod_wsgi-3.4-12.el7_0.i686.rpm | 75 kB 00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : mod_wsgi-3.4-12.el7_0.i686 1/1
Verifying : mod_wsgi-3.4-12.el7_0.i686 1/1
Installed:
mod_wsgi.i686 0:3.4-12.el7_0
Complete!
I guess the point I'm trying to make is that if you use version of software no available through yum you can experience unexpected results. I have been down this road before and I now use version of software only if they are available through yum.
The error you recieved: Requires: httpd-mmn = 20120211x8664 is for a package not yet available through yum. I performed a yum search on a CentOS 7.5 machine and it yields nothing available for httpd-mmn:
yum search httpd-mmn
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Warning: No matches found for: httpd-mmn
No matches found
So, you would have to compile it yourself possibly to get your setup to work.

FreeBSD pkg repository not updating and thinks it is up to date

I was installing a package using pkg and cancelled during the update check phase. I think this bugged it and now when I run pkg update it says it is on the latest versions. However, it most definitely is not.
Is there a way to force a clean repo list to pull the latest version info?
This is the error when I try to install php56 for example:
username#shavedbox:/usr/home/username # pkg install php56
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
The following 1 packages will be affected (of 0 checked):
New packages to be INSTALLED:
php56: 5.6.6
The process will require 15 MiB more space.
2 MiB to be downloaded.
Proceed with this action? [y/N]: y
pkg: http://pkg.FreeBSD.org/FreeBSD:10:amd64/latest/All/php56-5.6.6.txz: Not Found
(The most recent version is 5.6.7 so the file is obviously not found)
Any help is greatly appreciated! Not too used to FreeBSD...
The answer was simple.
pkg update -f
And then it worked fine. I need sleep.

CentOS yum 'No package gnuradio available'

I'm installing GNU Radio and following the instruction here
But everytime I try to do sudo yum install gnuradio, it says
Loaded plugins: fastestmirror, refresh-packagekit, security
Loading mirror speeds from cached hostfile
* base: centos.mirror.cdnetworks.com
* extras: centos.mirror.cdnetworks.com
* updates: centos.mirror.cdnetworks.com
Setting up Install Process
No package gnuradio available.
Error: Nothing to do
It's a fresh installed CentOS 6.5 and I've never edited CentOS yum repository information. What's wrong with gnuradio? They've removed the package from yum repository?
In their website, they provide several ways to install it including PyBOMBS. But I prefer yum. Building from source is somewhat bothering me so it's the last thing I will try.
By default CentOS does not include all the repositories needed by gnuradio and its dependencies.
You additionally need to configure/add at least RPMForge and Epel for your CentOS.
References:
http://wiki.centos.org/AdditionalResources/Repositories/RPMForge#head-f0c3ecee3dbb407e4eed79a56ec0ae92d1398e01
http://www.rackspace.com/knowledge_center/article/installing-rhel-epel-repo-on-centos-5x-or-6x
This is what I was told, but I have not yet tested this so cannot say is is correct for sure.

apt-get conflict in Ubuntu

I have tried to install mod_security, but it has the error, so I tried aptitude:
apt-get install libapache-mod-security
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libapache-mod-security : Depends: libapache2-modsecurity but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root#srv16540:~# aptitude install libapache2-modsecurity
The following NEW packages will be installed:
apache2.2-common{ab} libapache2-modsecurity modsecurity-crs{a}
0 packages upgraded, 3 newly installed, 0 to remove and 10 not upgraded.
Need to get 660 kB of archives. After unpacking 2,861 kB will be used.
The following packages have unmet dependencies:
apache2 : Conflicts: apache2.2-common but 2.2.22-1ubuntu1.4 is to be installed.
apache2.2-common : Depends: apache2.2-bin (= 2.2.22-1ubuntu1.4) but 2.4.6-2~precise+1 is installed.
apache2-bin : Conflicts: apache2.2-common but 2.2.22-1ubuntu1.4 is to be installed.
apache2-data : Conflicts: apache2.2-common but 2.2.22-1ubuntu1.4 is to be installed.
The following actions will resolve these dependencies:
**Keep the following packages at their current version:**
1) apache2.2-common [Not Installed]
2) libapache2-modsecurity [Not Installed]
3) modsecurity-crs [Not Installed]
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
I do now know what Keep the following packages at their current version means.
I want to know what does happen if I press yes. Does it replace my current apache2? Do I need to back up before doing this?
ANSWERS
I do now know what Keep the following packages at their current version mean
aptitude is trying to resolve the dependencies and possible conflicts to satisfy your installation request. It then proposes a solution. In your particular case the first solution it finds is to keep everything as it actually is, that's what keep at their current version + [Not installed] means.
I want to know what does happen if I press yes , does it replace my current apache2 ?
No, that solution will basically do nothing.
Do I need back up before ?
As boring as it sounds, backups are a good strategy to save time in the long run. If you're messing with important data then it should be even more important for you.
CONTEXT
I've seen other scenarios make aptitute propose solutions with combinations like these:
Remove the following packages
Keep the following packages at their current version
Leave the following dependencies unresolved
The following packages have been kept back
The following packages will be upgraded
The following packages were automatically installed and are no longer required
The following extra packages will be installed
Suggested packages
The following packages will be REMOVED
(and probably others)
In your case if instead of accepting the solution (or quitting), you reject it by pressing n, then aptitude will try to figure out another scenario that could be useful and propose it to you again. You can iterate through the solutions doing that and if any of them satisfies you then you can accept it.
SOLUTION (?)
As far as I can see by your output:
apache2.2-common : Depends: apache2.2-bin (= 2.2.22-1ubuntu1.4) but 2.4.6-2~precise+1 is installed.
Your problem is that you have apache2-2.4.6-2~precise+1 installed which isn't available from standard Ubuntu precise repositories (most probably installed from this PPA), and you're requesting a package which conflicts with that other one.
I'd take a look at the answers on how to remove PPAs and after you have removed that source I'd reinstall apache 2.2 from the standard repos with this command:
sudo aptitude install apache2
That's exactly what it did for me:
$ sudo apt-get remove apache2-bin
$ sudo apt-get autoremove
$ sudo apt-get install apache2
Open synaptic manager and search for apache2.2-bin. Mark it for removal. Then
sudo apt-get install apache2
Just remove all the content of /var/lib/apt/lists directory:
sudo rm -rf /var/lib/apt/lists/*
then run:
sudo apt-get update