I've installed mongoDB on fedora 17 and the server don't running.
I got the same error in this post MongoDB service not running in Fedora and then and try to fallow this instruction and I got another error
Trying to do this
yum --disablerepo=* --enablerepo=fedora,updates install mongodb mongodb-server
I got this Error
Transaction Check Error:
file /usr/bin/bsondump from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /usr/bin/mongo from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /usr/bin/mongodump from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /usr/bin/mongoexport from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /usr/bin/mongofiles from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /usr/bin/mongoimport from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /usr/bin/mongorestore from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /usr/bin/mongostat from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /usr/bin/mongotop from install of mongodb-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-2.0.6-mongodb_1.x86_64
file /etc/sysconfig/mongod from install of mongodb-server-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-server-2.0.6-mongodb_1.x86_64
file /usr/bin/mongod from install of mongodb-server-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-server-2.0.6-mongodb_1.x86_64
file /usr/bin/mongos from install of mongodb-server-2.0.2-10.fc17.x86_64 conflicts with file from package mongo-10gen-server-2.0.6-mongodb_1.x86_64
Error Summary
It looks as though you've already installed the 10gen packages for MongoDB 2.0.6. The conflicts are caused by trying to also install the default Fedora packaged version of MongoDB (2.0.2 from your error messages) which includes binaries with the same name.
Instead of reinstalling, you should be able to start the MongoDB service as root or using sudo:
service mongod start
With the 10gen packaged install you should find:
/etc/mongod.conf for changing configuration options
default data directory: /var/lib/mongo
default log file directory: /var/log/mongo
the init script at: /etc/rc.d/init.d/mongod
Related
I have a Raspberry Pi 4 running Raspian Lite Version 10. So I far I have installed git, Apache, php, and phpmyadmin on it.
Now while trying to install python3-venv package (or any package for that matter) using sudo apt-get install python3-venv I am getting following error -
Selecting previously unselected package python-pip-whl. dpkg: unrecoverable fatal error, aborting: files list file for package 'git' contains empty filename E: Sub-process /usr/bin/dpkg returned an error code (2)
I am not able to install any package on my system due to this error. So far I tried deleting the git folder from /usr/bin/dpkg but it has not seemed to help.
I was installing CM and CDH on CentOS6.9, some errors happended on one of the hosts.
So I want to reinstall cloudera-manager-agent, but failed.
Then I used rpm to reinstall(I had download the rpms), here is the result:
[root#xxx yum.repos.d]# rpm -e cloudera-manager*
error: package cloudera-manager-agent-5.12.0-1.cm5120.p0.120.el6.x86_64.rpm is not installed
error: package cloudera-manager-daemons-5.12.0-1.cm5120.p0.120.el6.x86_64.rpm is not installed
error: package cloudera-manager.repo is not installed
error: package cloudera-manager-server-5.12.0-1.cm5120.p0.120.el6.x86_64.rpm is not installed
error: package cloudera-manager-server-db-2-5.12.0-1.cm5120.p0.120.el6.x86_64.rpm is not installed
[root#vm8034 yum.repos.d]# rpm -U cloudera-manager*
error: cloudera-manager.repo: not an rpm package (or package manifest):
[root#vm8034 yum.repos.d]# rpm -U cloudera-manager*.rpm
package cloudera-manager-daemons-5.12.0-1.cm5120.p0.120.el6.x86_64 is already installed
package cloudera-manager-server-5.12.0-1.cm5120.p0.120.el6.x86_64 is already installed
package cloudera-manager-server-db-2-5.12.0-1.cm5120.p0.120.el6.x86_64 is already installed
package cloudera-manager-agent-5.12.0-1.cm5120.p0.120.el6.x86_64 is already installed
[root#xxx yum.repos.d]# rpm -q cloudera-manager*
package cloudera-manager-agent-5.12.0-1.cm5120.p0.120.el6.x86_64.rpm is not installed
package cloudera-manager-daemons-5.12.0-1.cm5120.p0.120.el6.x86_64.rpm is not installed
package cloudera-manager.repo is not installed
package cloudera-manager-server-5.12.0-1.cm5120.p0.120.el6.x86_64.rpm is not installed
package cloudera-manager-server-db-2-5.12.0-1.cm5120.p0.120.el6.x86_64.rpm is not installed
Try using yum instead of rpm and see if that works:
yum update cloudera-manager*
UPDATE:
Try a yum update. This will search for the available updates of your system and display a list with them. You can check if cloudera is in the list or not.
Then check the official website and see if there is any new version for download:
https://www.cloudera.com/downloads/manager/5-12-0.html
If there is try downloading the package, save it on your server and manually install it:
rpm -Uhv package-version-.rpm
Also you should check the content of /etc/yum.conf for an exclude = option. Usually that's used to exclude certain packages from update. If you find cloudera there, then that's why it will never update that package.
I have converted Debian package installation to CentOS RPM using alian. I'm getting below error when I try to install it.
Error:
file /etc/init.d from install of <package> conflicts with file from package chkconfig
I can install it by rpm -Uvh --force but I'm getting Not starting : <package> disabled. when I try to start it using init.d.
I'm not sure how to what is the correct path to track the issue. I appreciate some help.
To prevent the conflict you should exclude /etc/init.d from the .spec file. e.g.
%files
/etc
%exclude %dir /etc/init.d
This will only exclude the /etc/init.d directory. Any files under /etc/init.d/* will still be included.
When i was trying to install the latest mongodb-3.4.1 with tar fils, i encountered the following error:
libssl.so.10: cannot open shared object file: No such file or directory
then I searched from the net and tried this solution: https://askubuntu.com/questions/339364/libssl-so-10-cannot-open-shared-object-file-no-such-file-or-directory, created the soft link for the file libssl.so.1.0.0 and libcrypto.so.1.0.0, but another error occurred like this:
$ bin/mongod --config=mongo.cfg
bin/mongod: /lib/x86_64-linux-gnu/libcrypto.so.10: version `libcrypto.so.10' not found (required by bin/mongod)
bin/mongod: /lib/x86_64-linux-gnu/libssl.so.10: version `libssl.so.10' not found (required by bin/mongod)
The error was still there even though i reinstalled the libssl1.0.0 by apt-get install
On my Centos 6 server I updated curl using city-fan.repo but after installing I have issue with yum... I found ( after searching hours) that it was due to libssh2 older version so I removed it and downloaded again to recompile it, But to compile it GCC is not installed, When I try to ./configure libssh2-1.6.1-20150617 I have this error:
configure: error: no acceptable C compiler found in $PATH
, So I downloaded these packages from Centos repo as I am unable to use yum to install gcc:
cloog-ppl-0.15.7-1.2.el6.x86_64.rpm glibc-common-2.12-1.149.el6.x86_64.rpm kernel-headers-2.6.32-504.el6.x86_64.rpm
compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm gcc-4.4.7-11.el6.x86_64.rpm glibc-devel-2.12-1.149.el6.x86_64.rpm mpfr-2.4.1-6.el6.x86_64.rpm
cpp-4.4.7-11.el6.x86_64.rpm glibc-2.12-1.149.el6.x86_64.rpm glibc-headers-2.12-1.149.el6.x86_64.rpm ppl-0.10.2-11.el6.x86_64.rpm
When I try to install those I get this:
rpm -ivh *.rpm
Preparing... ########################################### [100%]
package glibc-common-2.12-1.149.el6_6.5.x86_64 (which is newer than glibc-common-2.12-1.149.el6.x86_64) is already installed
package glibc-2.12-1.149.el6_6.5.x86_64 (which is newer than glibc-2.12-1.149.el6.x86_64) is already installed
file /usr/sbin/build-locale-archive from install of glibc-common-2.12-1.149.el6.x86_64 conflicts with file from package glibc-common-2.12-1.149.el6_6.5.x86_64
file /usr/sbin/tzdata-update from install of glibc-common-2.12-1.149.el6.x86_64 conflicts with file from package glibc-common-2.12-1.149.el6_6.5.x86_64
file /lib64/ld-2.12.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /lib64/libc-2.12.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /lib64/libresolv-2.12.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /sbin/ldconfig from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /sbin/sln from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM1364.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM1371.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM1388.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM1390.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM1399.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM933.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM935.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM937.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/lib64/gconv/IBM939.so from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/sbin/glibc_post_upgrade.x86_64 from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/sbin/iconvconfig from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
file /usr/sbin/iconvconfig.x86_64 from install of glibc-2.12-1.149.el6.x86_64 conflicts with file from package glibc-2.12-1.149.el6_6.5.x86_64
and if I run any yum command it is displaying me this error:
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:
libssh2.so.1: cannot open shared object file: No such file or directory
Please install a package which provides this module, or
verify that the module is installed correctly.
It's possible that the above module doesn't match the
current version of Python, which is:
2.6.6 (r266:84292, Jan 22 2014, 09:42:36)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)]
If you cannot solve this problem yourself, please go to
the yum faq at:
http://yum.baseurl.org/wiki/Faq
I am very novice to this...Any help? Thanks
You have majorly hosed your system.
You downloaded rpm packages that are older than the ones you already have installed (that's what that error message is telling you).
Get the rpm packages for the libssh2 and curl packages you removed and fix yum.
Then find a better way to do whatever you were trying to do in the first place. Anything that requires you to upgrade a core component of the operating system (like libcurl) in a way that the official packages can't handle is broken by design.
have you tried doing the following:
yum provides libssh2.so.1
then installing one of the providing packages
e.g. yum install libssh2 ?