my version is 6.10 oracle linux
it is trying to istall both x86_64 and i686 packages
i am trying to install glibc package manually as it fails during my puppet run with exact same error as below:
yum install glibc-2.12-1.192.el6.i686
Loaded plugins: pulp-profile-update, security, ulninfo
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package glibc.i686 0:2.12-1.192.el6 will be installed
--> Processing Dependency: glibc-common = 2.12-1.192.el6 for package: glibc-2.12-1.192.el6.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.12-1.192.el6.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.12-1.192.el6.i686
--> Running transaction check
---> Package glibc.i686 0:2.12-1.192.el6 will be installed
--> Processing Dependency: glibc-common = 2.12-1.192.el6 for package: glibc-2.12-1.192.el6.i686
---> Package nss-softokn-freebl.i686 0:3.14.3-23.3.el6_8 will be installed
--> Finished Dependency Resolution
Error: Package: glibc-2.12-1.192.el6.i686 (nap_latest)
Requires: glibc-common = 2.12-1.192.el6
Installed: glibc-common-2.12-1.212.0.1.el6.x86_64 (#OL6Latest-x86_64/6.9)
glibc-common = 2.12-1.212.0.1.el6
Available: glibc-common-2.12-1.80.el6.x86_64 (nap_ol_base)
glibc-common = 2.12-1.80.el6
Available: glibc-common-2.12-1.107.el6_4.5.x86_64 (nap_latest)
glibc-common = 2.12-1.107.el6_4.5
Available: glibc-common-2.12-1.132.el6.x86_64 (nap_latest)
glibc-common = 2.12-1.132.el6
Available: glibc-common-2.12-1.132.el6_5.2.x86_64 (nap_latest)
glibc-common = 2.12-1.132.el6_5.2
Available: glibc-common-2.12-1.132.el6_5.4.x86_64 (nap_latest)
glibc-common = 2.12-1.132.el6_5.4
Available: glibc-common-2.12-1.149.el6.x86_64 (nap_latest)
glibc-common = 2.12-1.149.el6
Available: glibc-common-2.12-1.149.el6_6.5.x86_64 (nap_latest)
glibc-common = 2.12-1.149.el6_6.5
Available: glibc-common-2.12-1.149.el6_6.9.x86_64 (nap_latest)
glibc-common = 2.12-1.149.el6_6.9
Available: glibc-common-2.12-1.166.el6_7.3.x86_64 (nap_latest)
glibc-common = 2.12-1.166.el6_7.3
Available: glibc-common-2.12-1.166.el6_7.7.x86_64 (nap_latest)
glibc-common = 2.12-1.166.el6_7.7
Available: glibc-common-2.12-1.192.el6.x86_64 (nap_latest)
glibc-common = 2.12-1.192.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
any ideas? has anyone seen this previously?
You cannot install glibc-2.12-1.192.el6.i686 and glibc-2.12-1.212.0.1.el6.x86_64 in parallel. You will have to downgrade to glibc-2.12-1.192.el6.x86_64. With a proper repository configuration, this should work:
yum downgrade glibc-2.12-1.192.el6.x86_64
However, it is probably easier if you run yum upgrade and then simply install glibc.i686, without an explicit version.
(2.12-1.212.0.1.el6 is a strange version, by the way. Not sure what Oracle is doing there.)
ok here is what i did to get this to work:
yum -y downgrade glibc glibc-common
yum install -y glibc.i686 glibc-devel.i686 glibc-devel.x86_64 glibc-headers.x86_64
you should have something like this:
glibc.i686
glibc.x86_64
glibc-common.x86_64
glibc-devel.i686
glibc-devel.x86_64
glibc-headers.x86_64
if you still have problems check your repos
Related
I am attempting to install the libcap-devel library via yum, and it looks like my company's yum repo only has libcap-devel-2.22-8.el7.x86_64, which requires glibc-common-2.17-105.el7.
Unfortunately, the glibc-common installed on my VM is glibc-common-2.17-222.el7.x86_64, and the installation fails.
I want to figure out how to determine which version of libcap-devel is compatible with glibc-common-2.17-222.el7.x86_64, and then ask the sysadmins to add this verion of libcap-devel to the yum repo (which I am not authorized to do) so that I can install it successfully. How do I do this?
Here is the output of yum install libcap-devel
Resolving Dependencies
--> Running transaction check
---> Package libcap-devel.x86_64 0:2.22-8.el7 will be installed
--> Processing Dependency: libcap = 2.22-8.el7 for package: libcap-devel-2.22-8.el7.x86_64
--> Running transaction check
---> Package libcap.i686 0:2.22-8.el7 will be installed
--> Processing Dependency: libattr.so.1 for package: libcap-2.22-8.el7.i686
--> Processing Dependency: libattr.so.1(ATTR_1.0) for package: libcap-2.22-8.el7.i686
--> Processing Dependency: libc.so.6(GLIBC_2.8) for package: libcap-2.22-8.el7.i686
--> Running transaction check
---> Package glibc.i686 0:2.17-105.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-105.el7 for package: glibc-2.17-105.el7.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.17-105.el7.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-105.el7.i686
---> Package libattr.i686 0:2.4.46-12.el7 will be installed
--> Running transaction check
---> Package glibc.i686 0:2.17-105.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-105.el7 for package: glibc-2.17-105.el7.i686
---> Package nss-softokn-freebl.i686 0:3.16.2.3-13.el7_1 will be installed
--> Finished Dependency Resolution
You could try using --skip-broken to work around the problem
Error: Package: glibc-2.17-105.el7.i686 (redhat_base)
Requires: glibc-common = 2.17-105.el7
Installed: glibc-common-2.17-222.el7.x86_64 (#anaconda/7.5)
glibc-common = 2.17-222.el7
Available: glibc-common-2.17-105.el7.x86_64 (redhat_base)
glibc-common = 2.17-105.el7
Here is the output of yum --showduplicates list libcap-devel, which shows that the yum repo only has one version available:
========================== N/S matched: libcap-devel ===========================
libcap-devel-2.22-8.el7.i686 : Development files for libcap
libcap-devel-2.22-8.el7.x86_64 : Development files for libcap
The output of yum --showduplicates list libcap shows:
Installed Packages
libcap.x86_64 2.22-9.el7 #anaconda/7.5
Available Packages
libcap.i686 2.22-8.el7 redhat_base
libcap.x86_64 2.22-8.el7 redhat_base
The output of yum install -y libcap-2.22-8.el7.x86_64 shows:
Package matching libcap-2.22-8.el7.x86_64 already installed. Checking for update.
Nothing to do
After this, running yum install -y libcap-devel-2.22-8.el7.x86_64 still attempts to download the 32 bit version:
...
--> Processing Dependency: libcap = 2.22-8.el7 for package: libcap-devel-2.22-8.el7.x86_64
--> Running transaction check
---> Package libcap.i686 0:2.22-8.el7 will be installed
...
The output of yum --showduplicates list glibc shows glibc.i686 0:2.17-222.el7 is not available, only 2.17-105.e17 is.
Installed Packages
glibc.x86_64 2.17-222.el7 #anaconda/7.5
Available Packages
glibc.i686 2.17-105.el7 redhat_base
glibc.x86_64 2.17-105.el7 redhat_base
Any variation of this fails:
yum downgrade -y glibc-2.17-105.el7
yum downgrade -y glibc-2.17-105.el7 glibc-common-2.17-105.el7
yum downgrade -y glibc-2.17-105.el7 glibc-common-2.17-105.el7 glibc-devel-2.17-105.el7
yum downgrade -y glibc-headers-2.17-105.el7 glibc-2.17-105.el7 glibc-common-2.17-105.el7 glibc-devel-2.17-105.el7
For example the first command complains about glibc-common and glibc-devel, adding these in results in a complaint about glibc-headers, and the fourth line actually segfaults.
welcome to the jungle of library/rpm dependencies :)
It takes some time and patience to read, and then some skill to read the yum output. Sometimes you'll even have to run some intermediate commands to get the exact answer, but let's see what we can already see here:
Processing Dependency: libcap = 2.22-8.el7 for package: libcap-devel-2.22-8.el7.x86_64
You try to install libcap-devel. yum says he will also need to install libcap with the exact same version number. No surprises so far.
Package libcap.i686 0:2.22-8.el7 will be installed
This is probably already something you do not want. You seem to be on a 64 bit system; do you really want the i686 version of this library installed? The fact is libcap-devel does not say it requires the x86_64 version; it requires any of the two. Preferably yum will install the x86_64 version, but if that is impossible the i686 version will do.
In this case I would suggest you to first try installing libcap-2.22-8.el7.x86_64 and see why yum won't install that one.
But in any case let's just read on, this will give you also information on how to solve this problem for the x86_64 package.
--> Processing Dependency: libc.so.6(GLIBC_2.8) for package: libcap-2.22-8.el7.i686
--> Running transaction check
---> Package glibc.i686 0:2.17-105.el7 will be installed
so here yum chose to install glibc.i686 0:2.17-105.el7 , probably to satisfy the libc.so.6(GLIBC_2.8)
now this is where the conflict occurs: glibc.i686 0:2.17-105.el7 requires glibc-common with the exact same version number, but you already have a more recent version of glibc-common on your machine.
Possible solutions
There are multiple solutions here, a non-exhaustive list in order of my preference:
investigate why libcap-2.22-8.el7.x86_64 can't be installed.
make sure glibc.i686 0:2.17-222.el7 is available in your yum repositories (or installed on your system)
downgrade you glibc-common (and probably also glibc x86_64 version) to version 0:2.17-105.el7
Hello I'm newer using mongodb, and I'm following step Installing mongodb from web Installing mongodb enterprise on red hat
I'm use command:
sudo yum install -y mongodb-enterprise
and The terminal print:
Loaded plugins: product-id, refresh-packagekit, security, subscription-managerThis system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.Repository 'repository_url': Error parsing config: Error parsing "baseurl = 'repository_url'": URL must be http, ftp, file or https not ""Setting up Install ProcessResolving Dependencies--> Running transaction check---> Package mongodb-enterprise.x86_64 0:3.4.11-1.el6 will be installed--> Processing Dependency: mongodb-enterprise-tools = 3.4.11 for package: mongodb-enterprise-3.4.11-1.el6.x86_64--> Processing Dependency: mongodb-enterprise-shell = 3.4.11 for package: mongodb-enterprise-3.4.11-1.el6.x86_64--> Processing Dependency: mongodb-enterprise-server = 3.4.11 for package: mongodb-enterprise-3.4.11-1.el6.x86_64--> Processing Dependency: mongodb-enterprise-mongos = 3.4.11 for package: mongodb-enterprise-3.4.11-1.el6.x86_64--> Running transaction check---> Package mongodb-enterprise-mongos.x86_64 0:3.4.11-1.el6 will be installed---> Package mongodb-enterprise-server.x86_64 0:3.4.11-1.el6 will be installed--> Processing Dependency: openssl >= 1.0.1 for package: mongodb-enterprise-server-3.4.11-1.el6.x86_64---> Package mongodb-enterprise-shell.x86_64 0:3.4.11-1.el6 will be installed--> Processing Dependency: openssl >= 1.0.1 for package: mongodb-enterprise-shell-3.4.11-1.el6.x86_64---> Package mongodb-enterprise-tools.x86_64 0:3.4.11-1.el6 will be installed--> Processing Dependency: openssl >= 1.0.1 for package: mongodb-enterprise-tools-3.4.11-1.el6.x86_64--> Finished Dependency ResolutionError: Package: mongodb-enterprise-server-3.4.11-1.el6.x86_64 (mongodb-enterprise) Requires: openssl >= 1.0.1 Installed: openssl-1.0.0-27.el6.x86_64 (#anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4) openssl = 1.0.0-27.el6Error: Package: mongodb-enterprise-tools-3.4.11-1.el6.x86_64 (mongodb-enterprise) Requires: openssl >= 1.0.1 Installed: openssl-1.0.0-27.el6.x86_64 (#anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4) openssl = 1.0.0-27.el6Error: Package: mongodb-enterprise-shell-3.4.11-1.el6.x86_64 (mongodb-enterprise) Requires: openssl >= 1.0.1 Installed: openssl-1.0.0-27.el6.x86_64 (#anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4) openssl = 1.0.0-27.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
But I'm already installed openssl:
Command
openssl version
print:
OpenSSL 1.0.2n 7 Dec 2017
As you see I'm already installed openssl. So What is wrong with my step.
while trying to install "CPAN" using Yum command [CentOS 7.3(64-bit)] I am getting below error:
---> Package glibc.i686 0:2.17-157.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-157.el7 for package: glibc-2.17-157.el7.i686
---> Package kernel-headers.x86_64 0:3.10.0-514.el7 will be installed
---> Package nss-softokn-freebl.i686 0:3.16.2.3-14.4.el7 will be installed
--> Finished Dependency Resolution
Error: Package: glibc-2.17-157.el7.i686 (cent-7_1-os)
Requires: glibc-common = 2.17-157.el7
Installed: glibc-common-2.17-157.el7_3.4.x86_64 (#updates_latest)
glibc-common = 2.17-157.el7_3.4
Available: glibc-common-2.17-157.el7.x86_64 (cent-7_1-os)
glibc-common = 2.17-157.el7
Now on other hand when in run:
yum install glibc-2.17-157.el7.i686
It shows since I have already updated package:
Package matching glibc-2.17-157.el7.x86_64 already installed. Checking for update
how to work around this? for many of the Perl Modules is throws same error and requires glibc-2.17-157.el7.i686.
Below are list of some modules which throws the error (though there are many other packages which are throwing same error):
yum install perl-ExtUtils-Embed
yum install perl-ExtUtils-ParseXS
yum install perl-ExtUtils-Install
I have also tries to install using source packages, but no success :(
Please guide me if I am asking at wrong platform (No down votes plz)
It worked after changing the yum repo. I have edited the repository:
vim /etc/yum.repos.d/CentOS-Base.repo
And added below lines:
[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Previously it was :
[cent-7_1-os]
name=CentOS-7_1 - os
#baseurl=http://mhxrpmsrv001sas.dsone.3ds.com/rpms/cent/7_1/$basearch/os/latest/
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
enabled=1
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
priority=1
I think your glibc-common installed is of higher version than required.
first check if there is a version to downgrade to, by
yum list --showduplicates glibc
downgrade the glibc* by
yum downgrade glibc glibc-common glibc-devel glibc-headers
install gcc again
yum install gcc
Varnish 3 package is in the repo /etc/yum.repos.d/varnish.repo
When I do yum --enablerepo=varnish install varnish. It says repo doesn't exist.
[root#VR1gb yum.repos.d]# rpm -qf varnish.repo
varnish-release-3.0-1.el6.noarch
[root#VR1gb yum.repos.d]# yum --enablerepo=varnish-3.0 install varnish
It prompts to install Varnish 4 again if I do that. Same thing as I do.
[root#VR1gb yum.repos.d]# yum install varnish
Instruction on Varnish page clearly doesn't work.
https://www.varnish-cache.org/installation/redhat
Within varnish.repo
[root#VR1gb yum.repos.d]# cat varnish.repo
[varnish-3.0]
name=Varnish 3.0 for Enterprise Linux el6 - $basearch
baseurl=http://repo.varnish-cache.org/redhat/varnish-3.0/el6/$basearch
enabled=1
gpgcheck=0
#gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-VARNISH
yum --disablerepo=* --enablerepo=varnish-3.0 install varnish
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Resolving Dependencies
--> Running transaction check
---> Package varnish.x86_64 0:3.0.6-1.el6 will be installed
--> Processing Dependency: varnish-libs = 3.0.6-1.el6 for package: varnish-3.0.6-1.el6. x86_64
--> Processing Dependency: libpcre.so.0()(64bit) for package: varnish-3.0.6-1.el6.x86_64
--> Finished Dependency Resolution
Error: Package: varnish-3.0.6-1.el6.x86_64 (varnish-3.0)
Requires: varnish-libs = 3.0.6-1.el6
Installed: varnish-libs-4.0.2-1.el7.x86_64 (#epel)
varnish-libs = 4.0.2-1.el7
Available: varnish-libs-3.0.3-0.rc1.el6.x86_64 (varnish-3.0)
varnish-libs = 3.0.3-0.rc1.el6
Available: varnish-libs-3.0.3-1.el6.x86_64 (varnish-3.0)
varnish-libs = 3.0.3-1.el6
Available: varnish-libs-3.0.4-1.el6.x86_64 (varnish-3.0)
varnish-libs = 3.0.4-1.el6
Available: varnish-libs-3.0.5-1.el6.x86_64 (varnish-3.0)
varnish-libs = 3.0.5-1.el6
Available: varnish-libs-3.0.6-1.el6.x86_64 (varnish-3.0)
varnish-libs = 3.0.6-1.el6
Error: Package: varnish-3.0.6-1.el6.x86_64 (varnish-3.0)
Requires: libpcre.so.0()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root#VR1gb yum.repos.d]# rpm -qa 'varnish'
varnish-release-3.0-1.el6.noarch
[root#VR1gb yum.repos.d]# service varnish start
Starting varnish (via systemctl):
I'm running into problems installing Mongo using yum on CentOS. I've followed these instructions but am getting errors when installed the mongodb-org package:
$ sudo yum install mongodb-org
Loaded plugins: fastestmirror, presto
Loading mirror speeds from cached hostfile
* base: mirrors.cmich.edu
* extras: mirror.es.its.nyu.edu
* updates: mirror.kentdigital.net
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mongodb-org.x86_64 0:2.6.1-0.1.rc0 will be installed
--> Processing Dependency: mongodb-org-server = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-shell = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-mongos = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-tools = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Running transaction check
---> Package mongodb-org-mongos.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-server.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-shell.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-tools.x86_64 0:2.6.1-0.1.rc0 will be installed
--> Processing Conflict: mongodb-org-2.6.1-0.1.rc0.x86_64 conflicts mongo-10gen-server
--> Finished Dependency Resolution
Error: mongodb-org conflicts with mongodb-org-server
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
It seems like the mongodb package is conflicting with itself. Does anybody have an idea what's going on here? I can also confirm that there are no other mongo packages currently installed on the machine.
I just ran into the same problem. Ernie Hershey from MongoDB helped me resolve it by answering my post in the MongoDB user group:
https://groups.google.com/forum/#!topic/mongodb-user/5xRQW7ER4hE
You basically need to run yum makecache before running yum install mongodb-org because of a bug in how MongoDB RC packages are generated. That solved the problem for me.