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.
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
I am trying to install Chrome using :
sudo yum localinstall -y https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm
but every time I am getting this error:
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Examining /var/tmp/yum-root-FKPkpJ/google-chrome-stable_current_x86_64.rpm: google-chrome-stable-67.0.3396.62-1.x86_64
Marking /var/tmp/yum-root-FKPkpJ/google-chrome-stable_current_x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package google-chrome-stable.x86_64 0:67.0.3396.62-1 will be installed
--> Processing Dependency: /usr/bin/lsb_release for package: google-chrome-stable-67.0.3396.62-1.x86_64
--> Processing Dependency: libappindicator3.so.1()(64bit) for package: google-chrome-stable-67.0.3396.62-1.x86_64
--> Processing Dependency: /usr/bin/lsb_release for package: google-chrome-stable-67.0.3396.62-1.x86_64
--> Finished Dependency Resolution
Error: Package: google-chrome-stable-67.0.3396.62-1.x86_64 (/google-chrome-stable_current_x86_64)
Requires: libappindicator3.so.1()(64bit)
Error: Package: google-chrome-stable-67.0.3396.62-1.x86_64 (/google-chrome-stable_current_x86_64)
Requires: /usr/bin/lsb_release
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Please Help.
Taken from https://access.redhat.com/discussions/917293
wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm
yum -y install redhat-lsb libXScrnSaver
yum -y localinstall google-chrome-stable_current_x86_64.rpm
Problem solved. I just had to use subscription-manager to subscribe and register my system and also update yum with yum check-update.
I am getting conflict when
[root#MongoDB ec2-user]# sudo yum install mongodb-org Loaded plugins:
priorities, security, update-motd, upgrade-helper Setting up Install
Process Resolving Dependencies
--> Running transaction check
---> Package mongodb-org.x86_64 0:2.6.0-1 will be installed
--> Processing Dependency: mongodb-org-tools = 2.6.0 for package: mongodb-org-2.6.0-1.x86_64
--> Processing Dependency: mongodb-org-shell = 2.6.0 for package: mongodb-org-2.6.0-1.x86_64
--> Processing Dependency: mongodb-org-server = 2.6.0 for package: mongodb-org-2.6.0-1.x86_64
--> Processing Dependency: mongodb-org-mongos = 2.6.0 for package: mongodb-org-2.6.0-1.x86_64
--> Running transaction check
---> Package mongodb-org-mongos.x86_64 0:2.6.0-1 will be installed
---> Package mongodb-org-server.x86_64 0:2.6.0-1 will be installed
---> Package mongodb-org-shell.x86_64 0:2.6.0-1 will be installed
---> Package mongodb-org-tools.x86_64 0:2.6.0-1 will be installed
--> Processing Conflict: mongodb-org-tools-2.6.0-1.x86_64 conflicts mongo-10gen-server
--> Processing Conflict: mongodb-org-tools-2.6.0-1.x86_64 conflicts mongo-10gen
--> Processing Conflict: mongodb-org-mongos-2.6.0-1.x86_64 conflicts mongo-10gen-server
--> Processing Conflict: mongodb-org-mongos-2.6.0-1.x86_64 conflicts mongo-10gen
--> Processing Conflict: mongodb-org-shell-2.6.0-1.x86_64 conflicts mongo-10gen-server
--> Processing Conflict: mongodb-org-shell-2.6.0-1.x86_64 conflicts mongo-10gen
--> Processing Conflict: mongodb-org-2.6.0-1.x86_64 conflicts mongo-10gen-server
--> Processing Conflict: mongodb-org-2.6.0-1.x86_64 conflicts mongo-10gen
--> Processing Conflict: mongodb-org-server-2.6.0-1.x86_64 conflicts mongo-10gen-server
--> Processing Conflict: mongodb-org-server-2.6.0-1.x86_64 conflicts mongo-10gen
--> Finished Dependency Resolution Error: mongodb-org-shell conflicts with mongo-10gen-2.4.10-mongodb_1.x86_64 Error: mongodb-org-server
conflicts with mongo-10gen-server-2.4.10-mongodb_1.x86_64 Error:
mongodb-org-mongos conflicts with mongo-10gen-2.4.10-mongodb_1.x86_64
Error: mongodb-org-mongos conflicts with
mongo-10gen-server-2.4.10-mongodb_1.x86_64 Error: mongodb-org-tools
conflicts with mongo-10gen-2.4.10-mongodb_1.x86_64 Error:
mongodb-org-server conflicts with mongo-10gen-2.4.10-mongodb_1.x86_64
Error: mongodb-org-tools conflicts with
mongo-10gen-server-2.4.10-mongodb_1.x86_64 Error: mongodb-org
conflicts with mongo-10gen-server-2.4.10-mongodb_1.x86_64 Error:
mongodb-org conflicts with mongo-10gen-2.4.10-mongodb_1.x86_64 Error:
mongodb-org-shell conflicts with
mongo-10gen-server-2.4.10-mongodb_1.x86_64 You could try using
--skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
and update giving this error:
sudo yum update mongodb-org Loaded plugins: priorities, security,
update-motd, upgrade-helper amzn-main
| 2.1 kB 00:00 amzn-updates
| 2.3 kB 00:00 Setting up Update Process Package(s)
mongodb-org available, but not installed.
How can i fix this ?
Since the package name has changed, you do need to remove the old package and install the new one. However, instead of doing this as two steps, it is cleaner to use the yum shell. This will remove the old package and install the new one in a single transaction:
yum shell
> install mongodb-org
> remove mongo-10gen
> remove mongo-10gen-server
> run
--> Running transaction check
---> Package mongo-10gen.i686 0:2.4.10-mongodb_1 will be erased
---> Package mongo-10gen-server.i686 0:2.4.10-mongodb_1 will be erased
---> Package mongodb-org.i686 0:2.6.0-1 will be installed
--> Processing Dependency: mongodb-org-tools = 2.6.0 for package: mongodb-org-2.6.0-1.i686
--> Processing Dependency: mongodb-org-shell = 2.6.0 for package: mongodb-org-2.6.0-1.i686
--> Processing Dependency: mongodb-org-server = 2.6.0 for package: mongodb-org-2.6.0-1.i686
--> Processing Dependency: mongodb-org-mongos = 2.6.0 for package: mongodb-org-2.6.0-1.i686
--> Running transaction check
---> Package mongodb-org-mongos.i686 0:2.6.0-1 will be installed
---> Package mongodb-org-server.i686 0:2.6.0-1 will be installed
---> Package mongodb-org-shell.i686 0:2.6.0-1 will be installed
---> Package mongodb-org-tools.i686 0:2.6.0-1 will be installed
--> Finished Dependency Resolution
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
mongodb-org i686 2.6.0-1 10gen 4.6 k
Removing:
mongo-10gen i686 2.4.10-mongodb_1 #10gen 181 M
mongo-10gen-server i686 2.4.10-mongodb_1 #10gen 30 M
Installing for dependencies:
mongodb-org-mongos i686 2.6.0-1 10gen 6.7 M
mongodb-org-server i686 2.6.0-1 10gen 8.9 M
mongodb-org-shell i686 2.6.0-1 10gen 4.2 M
mongodb-org-tools i686 2.6.0-1 10gen 88 M
Transaction Summary
================================================================================
Install 1 Package (+4 Dependent packages)
Remove 2 Packages
Total download size: 108 M
Is this ok [y/d/N]: y
Downloading packages:
(1/5): mongodb-org-2.6.0-1.i686.rpm | 4.6 kB 00:00
(2/5): mongodb-org-mongos-2.6.0-1.i686.rpm | 6.7 MB 00:00
(3/5): mongodb-org-server-2.6.0-1.i686.rpm | 8.9 MB 00:00
(4/5): mongodb-org-shell-2.6.0-1.i686.rpm | 4.2 MB 00:00
(5/5): mongodb-org-tools-2.6.0-1.i686.rpm | 88 MB 00:04
--------------------------------------------------------------------------------
Total 19 MB/s | 108 MB 00:05
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : mongodb-org-server-2.6.0-1.i686 1/7
Installing : mongodb-org-mongos-2.6.0-1.i686 2/7
Installing : mongodb-org-tools-2.6.0-1.i686 3/7
Installing : mongodb-org-shell-2.6.0-1.i686 4/7
Installing : mongodb-org-2.6.0-1.i686 5/7
Erasing : mongo-10gen-server-2.4.10-mongodb_1.i686 6/7
Erasing : mongo-10gen-2.4.10-mongodb_1.i686 7/7
Verifying : mongodb-org-2.6.0-1.i686 1/7
Verifying : mongodb-org-shell-2.6.0-1.i686 2/7
Verifying : mongodb-org-tools-2.6.0-1.i686 3/7
Verifying : mongodb-org-mongos-2.6.0-1.i686 4/7
Verifying : mongodb-org-server-2.6.0-1.i686 5/7
Verifying : mongo-10gen-server-2.4.10-mongodb_1.i686 6/7
Verifying : mongo-10gen-2.4.10-mongodb_1.i686 7/7
Removed:
mongo-10gen.i686 0:2.4.10-mongodb_1
mongo-10gen-server.i686 0:2.4.10-mongodb_1
Installed:
mongodb-org.i686 0:2.6.0-1
Dependency Installed:
mongodb-org-mongos.i686 0:2.6.0-1 mongodb-org-server.i686 0:2.6.0-1
mongodb-org-shell.i686 0:2.6.0-1 mongodb-org-tools.i686 0:2.6.0-1
Finished Transaction
> exit
Leaving Shell
You have to remove packages of MongoDB 2.4:
sudo yum remove mongo-10gen*
and then install packages of new MongoDB 2.6:
sudo yum install mongodb-org
Seems that you are upgrading from version 2.4 to 2.6 which apparently has changed the package names.
I guess you will have to remove/erase the old package mongodb-10gen* and then run this new install command for it to work.
remove the old mongodb
sudo yum remove mongo-10gen-server mongo-10gen-tools mongo-10gen-shell mongo-10gen-mongos mongo-10gen
install the new mongodb (prerequisitely, you must config the yum source, refer here )
sudo yum install mongodb-org
We are trying to install CDH 4.4 on RHEL 5.7. But the installation was aborted because of Postgres DB installation issues.
Logs from /var/log/cloudera-manager-installer/4.install-cloudera-manager-server-db.log
Loaded plugins: product-id, security, subscription-manager Updating Red Hat repositories. Setting up Install Process Resolving Dependencies
--> Running transaction check
---> Package cloudera-manager-server-db.x86_64 0:4.7.3-1.cm473.p0.163.el5 set to be updated
--> Processing Dependency: postgresql-server >= 8.0 for package: cloudera-manager-server-db
--> Finished Dependency Resolution cloudera-manager-server-db-4.7.3-1.cm473.p0.163.el5.x86_64 from cloudera-manager has depsolving problems
--> Missing Dependency: postgresql-server >= 8.0 is needed by package cloudera-manager-server-db-4.7.3-1.cm473.p0.163.el5.x86_64 (cloudera-manager) Error: Missing Dependency: postgresql-server >= 8.0 is needed by package cloudera-manager-server-db-4.7.3-1.cm473.p0.163.el5.x86_64 (cloudera-manager) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package.
Please let me know how to proceed further.
Configure the YUM in your local or use any public Repo to install the dependencies.
When installing freenx server problem, complaining that there is no /usr/lib64/nx.
Established as follows:
> yum install nx freenx
But in the console log:
[root#q182 ~]# yum install nx freenx
Loaded plugins: fastestmirror, refresh-packagekit, security
Loading mirror speeds from cached hostfile
* base: mirror.netcologne.de
* epel: mirror.imt-systems.com
* extras: mirror.netcologne.de
* rpmforge: mirror1.hs-esslingen.de
* updates: mirror.netcologne.de
Setting up Install Process
Package nx-3.5.0-2.1.el6.centos.x86_64 already installed and latest version
Package freenx is obsoleted by freenx-server, trying to install freenx-server-0.7.3-18.el6.x86_64 instead
Resolving Dependencies
--> Running transaction check
---> Package freenx-server.x86_64 0:0.7.3-18.el6 will be installed
--> Processing Dependency: /usr/lib64/nx for package: freenx-server-0.7.3-18.el6.x86_64
--> Processing Dependency: /usr/lib64/nx for package: freenx-server-0.7.3-18.el6.x86_64
--> Finished Dependency Resolution
Error: Package: freenx-server-0.7.3-18.el6.x86_64 (atrpms)
Requires: /usr/lib64/nx
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root#q182 ~]#
Just add --enablerepo=atrpms-bleeding to your yum command and the nx dependency will install from there.