I'm trying to update some code I am running on PythonAnywhere, but am having some network issues.
When I try and pull from git or install from pip I keep getting errors.
(my-site)04:02 ~/my-site (master)$ git pull
fatal: unable to access 'https://github.com/LegoStormtroopr/possum-mdr.git/': Failed connect to github.com:3128; Connection refused
(my-site)04:02 ~/my-site (master)$ pip install django_select2
Downloading/unpacking django-select2
Cannot fetch index base URL https://pypi.python.org/simple/
Could not find any downloads that satisfy the requirement django-select2
No distributions at all found for django-select2
Storing complete log in /home/my-site/.pip/pip.log
Has anyone else experienced this?
Related
I cannot install pglogical. I'm fallowing this tutorial: https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql-full-load-pglogical.html#chap-manageddatabases.postgresql-rds-postgresql-full-load-pglogical-replication
And part about pglogical installation has two steps (I'm using postgres 10.4):
curl https://access.2ndquadrant.com/api/repository/dl/default/release/10/rpm | bash
yum install postgresql10-pglogical
I'm getting an error though:
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
https://dl.2ndquadrant.com/default/release/rpm/packages/amzn/2/x86_64/10/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
One of the configured repositories failed (2ndQuadrant packages (PG10) for 2 - x86_64),
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=2ndquadrant-dl-default-release-pg10 ...
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 2ndquadrant-dl-default-release-pg10
or
subscription-manager repos --disable=2ndquadrant-dl-default-release-pg10
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=2ndquadrant-dl-default-release-pg10.skip_if_unavailable=true
failure: repodata/repomd.xml from 2ndquadrant-dl-default-release-pg10: [Errno 256] No more mirrors to try.
https://dl.2ndquadrant.com/default/release/rpm/packages/amzn/2/x86_64/10/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
How can I install it?
Running on centos 8 today want to install new package and before it wants to run:
yum update -y
but got this:
Failed to download metadata for repo 'appstream': Cannot prepare
internal mirrorlist: No URLs in mirrorlist
Then I did search and found a solution to fix it:
sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS-*
sed -i 's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*
I did this but still error persist, any idea? how to fix this? Is there new solution in 2022?
After use this solution
Now error:
Errors during downloading metadata for repository 'extras':
Status code: 403 for https://vault.centos.org/centos/8/extras/x86_64/os/repodata/repomd.xml
(IP: 13.249.9.66) Error: Failed to download metadata for repo
'extras': Cannot download repomd.xml: Cannot download
repodata/repomd.xml: All mirrors were tried
I am using Redhat Linux server and trying to install the MongoDB on it.
I am following steps given in the link: https://docs.mongodb.com/manual/tutorial/install-mongodb-on-red-hat/
Step 1: Create a /etc/yum.repos.d/mongodb-org-4.0.repo file so that you can install MongoDB directly, using yum.
sudo nano /etc/yum.repos.d/mongodb-org-4.0.repo
Step 2: Copy and paste below code in the newly created file.
[mongodb-org-4.0]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/4.0/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-4.0.asc
Step 3: To install a specific release of MongoDB, specify each component package individually and append the version number to the package name, as in the following example:
sudo yum install -y mongodb-org
After all this I am getting an error given below:
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
file:///packages/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /packages/repodata/repomd.xml"
Trying other mirror.`
One of the configured repositories failed (local),
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=localrepo ...
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 localrepo
or
subscription-manager repos --disable=localrepo
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=localrepo.skip_if_unavailable=true
failure: repodata/repomd.xml from localrepo: [Errno 256] No more mirrors to try.
file:///packages/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /packages/repodata/repomd.xml"
Server OS
NAME="Red Hat Enterprise Linux Server"
VERSION="7.3 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.3"
PRETTY_NAME="Red Hat Enterprise Linux"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.3:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.3
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.3"
I already followed steps below but these are not working in my case:
sudo rm -rf /etc/yum.repos.d/mongodb-org-4.0.repo
sudo yum clean all
How could i resolve this error?
Based on your error message it looks like you had a nameserver problem, which can involve a variety of solutions as this answer from redhat.com describes. My mongodb-org-4.0.repo file looks just like yours except with version 4.4 and everything worked fine. Well not at first that's how I found this post, but my problem was a blank space I accidentally inserted at the end of the mongodb-org-4.4.repo file.
I found this Unix & Linux Stack Exchange post with some possible fixes, one of which is updating to the latest CentOS. This ServerFault post also had an Errno 14 error message like you're seeing, but this solution was to disable SELinux.
you should check with baseurl in /etc/yum.repos.d/mongodb-org-4.0.repo file. we can also change the releaseserver version in baseurl.
Here is my /etc/yum.repos.d/mongodb-org-4.0.repo file
[mongodb-org-4.0]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/7/mongodb-org/4.0/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-4.0.asc
It works for me.
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.
I am trying to install rvm from the official install page.
Running this is broken:
bash < <(curl -s https://rvm.beginrescueend.com/install/rvm)
fatal: unable to connect a socket (Connection refused)
Initialized empty Git repository in /home/ghufran/.rvm/src/rvm/.git/
fatal: https://github.com/wayneeseguin/rvm.git/info/refs download error - The requested URL returned error: 403
ERROR: Unable to clone the RVM repository, attempted both git:// and https://
I am using ubuntu 9.1 64 bit.
So after looking into this, i figured out it wasn't related to rvm at all.
The problem was with my network and the port used for git protocol was not open. Opening the port worked for me.
base on the tutorial here
did you install all the development libraries like:
$ sudo apt-get install zlib1g-dev libreadline5-dev libssl-dev
libxml2-dev
??
I just installed rvm successfully following the tutorial I just mentioned on my Ubuntu 11.04 box. and I don't think the version of the OS is a big problem.
beside, there is NO Ubuntu 9.1, it's Ubuntu 9.10, which means released Oct, 2009.