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
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.
Getting following error:
error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
Already tried installing using below cmd:
sudo apt-get install ia32-libs-gtk
Getting error for this too:E: Unable to locate package ia32-libs-gtk
Seems you need to install x86 version:
sudo apt-get install libgtk2.0-0:i386
I installed the Ripple rpm repo following documentation
(step 1)
$ sudo rpm -Uvh
https://mirrors.ripple.com/ripple-repo-el7.rpm
Then (step2) I run command:
sudo yum install --enablerepo=ripple-stable rippled
but I get the error:
https://mirrors.ripple.com/rpm/%24releasever/stable/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: ripple-stable. Please verify its path and try again
Does anyone know how to resolve it?
That error message occurs when attempting to install the rippled package on an unsupported environment.
The rippled rpm package is currently only available for CentOS/RHEL 7 (and Ubuntu 15+ using alien)
You could try installing with:
sudo yum install --enablerepo=ripple-stable --releasever=el7 rippled
but YMMV.
\The URL is suspect - it says %24releasever which is URL-encoded $releasever which means your yum isn't filling in that blank, e.g. .../rpm/7/stable/.
Try hard-coding it in the file you can find in /etc/yum.repos.d/ that your step one installed.
Overview
I was creating my Docker image to setup Rockmongo.
In the Dockerfile, I have a command
pecl install mongo
This command was working before but when ran t today I am getting this error,
downloading mongo-1.5.5.tgz ...
Starting to download mongo-1.5.5.tgz (Unknown size)
....done: 3,582 bytes
Could not get contents of package "/build/buildd/php5-5.3.10/pear-build-download/mongo-1.5.5.tgz". Invalid tgz file.
Download of "pecl/mongo" succeeded, but it is not a valid package archive
Error: cannot download "pecl/mongo"
Reference
To view the whole docker file
https://github.com/gilacode/docker-rockmongo/blob/master/Dockerfile
Question
Is there any way to specificy a different version of the Mongo package during the "pecl install command"?
I see this is an old question but anyway ...
I had the same issue and it was not due to the pecl website.
It seems to be a bug with the "lfs" option when you compile php5.
To verify if this is your case type: php-config --phpapi
I got it working by adding the --nocompress option
[sudo pecl install --nocompress mongo]
You can see other details here https://bugs.php.net/bug.php?id=67075
I have a really strange issue with the behavior of pip in a virtualenv.
I have set
export PIP_REQUIRE_VIRTUALENV=true
export PIP_DOWNLOAD_CACHE=$HOME/.pip/cache
export VIRTUALENV_DISTRIBUTE=true
Now, when I'm in my virtualenv and want to install my dependencies:
pip install -r requirements/_base.txt
(for testing purposes, requirements/_base.txt only contains:)
Django==1.5
Anyway, when I try to install it, I only get:
Downloading/unpacking Django==1.5 (from -r requirements/_base.txt (line 1))
Running setup.py egg_info for package Django
warning: no previously-included files matching '__pycache__' found under directory '*'
warning: no previously-included files matching '*.py[co]' found under directory '*'
And after that, Django is not installed.
Here comes the strange part: When I install Django manually with
pip install Django==1.5
it's working perfectly (though the same two warnings appear):
Downloading/unpacking Django==1.5
Running setup.py egg_info for package Django
warning: no previously-included files matching '__pycache__' found under directory '*'
warning: no previously-included files matching '*.py[co]' found under directory '*'
Installing collected packages: Django
Running setup.py install for Django
changing mode of build/scripts-2.7/django-admin.py from 644 to 755
warning: no previously-included files matching '__pycache__' found under directory '*'
warning: no previously-included files matching '*.py[co]' found under directory '*'
changing mode of /usr/local/share/python/django-admin.py to 755
Successfully installed Django
Cleaning up...
I faced a similar problem and realized that removing the version requirement solved the problem. Don't know why though...
I figured out why this was happening to me, which may also solve the problem for others who see this page. For me, the problem was that I had a requirement that can not install automatically via pip. The pip freeze exported the package name and version but, for whatever reason, pip cannot install that package directly in a requirements install. I have to instead install it manually from a zip file.
The problem you might be experiencing, then, is that you have a requirement which cannot be installed by pip's requirements installer. Check your output log for red text, errors, that sort of thing.
I figured this out using this post:
pip fails to install packages from requirements.txt