New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Several curl errors while downloading packages using `qubes-dom0-update` #3693

Open
SaswatPadhi opened this Issue Mar 12, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@SaswatPadhi

SaswatPadhi commented Mar 12, 2018

Qubes OS version:

4.0~rc5

Affected component(s):

qubes-dom0-update


Steps to reproduce the behavior:

sudo qubes-dom0-update gparted

Expected behavior:

Downloads happen as usual

Actual behavior:

I see several warnings from curl:

.
.
.
DNF will only download packages for the transaction.
Downloading Packages:
[MIRROR] gparted-0.28.1-1.fc25.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Mon, 12 Mar 2018 04:16:45 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">/Packages/g/gparted-0.28.1-1.fc25.x86_64.rpm [Could not resolve host: <metalink version="3.0" xmlns="http]
[MIRROR] gparted-0.28.1-1.fc25.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://<url protocol="rsync" type="rsync" location="US" preference="100" >rsync://mirror.sfo12.us.leaseweb.net/fedora/updates/25/x86_64/repodata/repomd.xml</url>/Packages/g/gparted-0.28.1-1.fc25.x86_64.rpm [Could not resolve host: <url protocol="rsync" type="rsync" location="US" preference="100" >rsync]
[MIRROR] gparted-0.28.1-1.fc25.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://<url protocol="http" type="http" location="US" preference="100" >http://mirror.sfo12.us.leaseweb.net/fedora/linux/updates/25/x86_64/repodata/repomd.xml</url>/Packages/g/gparted-0.28.1-1.fc25.x86_64.rpm [Could not resolve host: <url protocol="http" type="http" location="US" preference="100" >http]
[MIRROR] gparted-0.28.1-1.fc25.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://<url protocol="http" type="http" location="US" preference="99" >http://mirror.uoregon.edu/fedora/linux/updates/25/x86_64/repodata/repomd.xml</url>/Packages/g/gparted-0.28.1-1.fc25.x86_64.rpm [Could not resolve host: <url protocol="http" type="http" location="US" preference="99" >http]
.
.
.
gparted-0.28.1-1.fc25.x86_64.rpm                1.2 MB/s | 1.9 MB     00:01    
--------------------------------------------------------------------------------
Total                                           756 kB/s | 1.9 MB     00:02     
Complete!
The downloaded packages were saved in cache until the next successful transaction.

General notes:

I tried both with and without fastestmirror=1 in my /etc/dnf/dnf.conf -- same behavior.

@SaswatPadhi SaswatPadhi changed the title from Several curl errors while running downloading packages using `qubes-dom0-update` to Several curl errors while downloading packages using `qubes-dom0-update` Mar 12, 2018

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Mar 12, 2018

@esote

This comment has been minimized.

Show comment
Hide comment
@esote

esote Mar 22, 2018

I've just had an issue similar to this one recently on 3.2. I don't know if it is related to the fact that I've recently re-created my sys-firewall AppVM.

I would run:

sudo qubes-dom0-update

And receive the error:

Checking for dom0 updates...
Failed to synchronize cache for repo 'qubes-dom0-current', disabling.
No new updates available

To debug it, I ran qubes-dom0-update --action="-v update --refresh"

It spouted a dozen or so errors all similar to this one:

error: Curl error (6): Couldn't resolve host name for http://<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Thu, 22 Mar 2018 00:12:11 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">/repodata/repomd.xml [Could not resolve host: <metalink version="3.0" xmlns="http] (http://<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Thu, 22 Mar 2018 00:12:11 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">/repodata/repomd.xml).

However, despite those errors, running that command above (qubes-dom0-update with the flag --action="-v update --refresh") seems to have fixed it for me.

esote commented Mar 22, 2018

I've just had an issue similar to this one recently on 3.2. I don't know if it is related to the fact that I've recently re-created my sys-firewall AppVM.

I would run:

sudo qubes-dom0-update

And receive the error:

Checking for dom0 updates...
Failed to synchronize cache for repo 'qubes-dom0-current', disabling.
No new updates available

To debug it, I ran qubes-dom0-update --action="-v update --refresh"

It spouted a dozen or so errors all similar to this one:

error: Curl error (6): Couldn't resolve host name for http://<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Thu, 22 Mar 2018 00:12:11 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">/repodata/repomd.xml [Could not resolve host: <metalink version="3.0" xmlns="http] (http://<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Thu, 22 Mar 2018 00:12:11 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">/repodata/repomd.xml).

However, despite those errors, running that command above (qubes-dom0-update with the flag --action="-v update --refresh") seems to have fixed it for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment