Dnf stopped working

, ,

My dnf issue appears different from the ones I have looked at in this forum, hence the new thread.

Any DNF command I enter e.g:

dnf install 
dnf up
dnf upgrade
dnf repoclosure
dnf distrosync

…returns the same result:

Copr repo for llvm-snapshots owned by @fedora-l 5.0 kB/s | 3.0 kB     00:00    
Fedora 36 - x86_64                              0.0  B/s |   0  B     06:00    
Fedora 36 - x86_64                              0.0  B/s |   0  B     06:00  

Errors during downloading metadata for repository 'fedora':

  - Curl error (6): Couldn't resolve host name for http://download.example/pub/fedora/linux/releases/36/Everything/x86_64/os/repodata/repomd.xml [Could not resolve host: download.example]

  - Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64 [Connection timeout after 30000 ms]
Error: Failed to download metadata for repo 'fedora': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

As you can see, it times out after ~ 12 minutes.

The Software Repository will also not update.

Possible relevant information:

  • I did not update Fedora 35 prior to installing Fedora 36

  • I do have Python 3.10.4 and Anaconda 36.16.5 installed, however they are installed in my home directory, not in the root directory.

  • As it appears to be a download problem I de-activated my VPN, yet the problem persists.

FWIW I append the results of…

(base) [ra@fedora-main-drive ~]$ rpm -qa \*dnf\* \*repo\*
libreport-filesystem-2.17.1-1.fc36.noarch
dnf-data-4.12.0-1.fc36.noarch
fedora-repos-36-1.noarch
libreport-2.17.1-1.fc36.x86_64
libreport-web-2.17.1-1.fc36.x86_64
libreport-plugin-bugzilla-2.17.1-1.fc36.x86_64
libreport-plugin-ureport-2.17.1-1.fc36.x86_64
libreport-plugin-reportuploader-2.17.1-1.fc36.x86_64
libreport-cli-2.17.1-1.fc36.x86_64
libreport-fedora-2.17.1-1.fc36.x86_64
libreport-plugin-logger-2.17.1-1.fc36.x86_64
librepo-1.14.3-1.fc36.x86_64
libdnf-0.67.0-2.fc36.x86_64
python3-libdnf-0.67.0-2.fc36.x86_64
libreport-anaconda-2.17.1-1.fc36.x86_64
libreport-plugin-kerneloops-2.17.1-1.fc36.x86_64
libreport-plugin-systemd-journal-2.17.1-1.fc36.x86_64
createrepo_c-libs-0.20.0-1.fc36.x86_64
createrepo_c-0.20.0-1.fc36.x86_64
python3-dnf-4.12.0-1.fc36.noarch
python3-libreport-2.17.1-1.fc36.x86_64
dnf-4.12.0-1.fc36.noarch
dnfdaemon-selinux-0.3.20-8.fc36.noarch
dnfdaemon-0.3.20-8.fc36.noarch
python3-dnfdaemon-0.3.20-8.fc36.noarch
python3-dnf-plugins-core-4.2.0-1.fc36.noarch
dnf-plugins-core-4.2.0-1.fc36.noarch
python3-dnf-plugins-extras-common-4.0.16-1.fc36.noarch
libreport-gtk-2.17.1-1.fc36.x86_64
dnfdragora-2.1.2-1.fc36.noarch
python3-dnf-plugin-system-upgrade-4.0.16-1.fc36.noarch
dnf-utils-4.2.0-1.fc36.noarch
fedora-workstation-repositories-35-3.fc36.noarch
fedora-repos-modular-36-1.noarch
1 Like

That’s not a valid repository link (download.example is an example URL). Have you made any changes to your repository files in /etc/yum.repos.d/? Can you please post the contents of the /etc/yum.repos.d/fedora.repo file?

1 Like

Yes, I was suspicious of “download.example”, it’s a reserved top-level domain name. I never put it in this read-only file myself.

Contents of fedora.repo

[fedora]
name=Fedora $releasever - $basearch
baseurl=http://download.example/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch
enabled=1
countme=1
metadata_expire=7d
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[fedora-debuginfo]
name=Fedora $releasever - $basearch - Debug
baseurl=http://download.example/pub/fedora/linux/releases/$releasever/Everything/$basearch/debug/tree/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-$releasever&arch=$basearch
enabled=0
metadata_expire=7d
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[fedora-source]
name=Fedora $releasever - Source
#baseurl=http://download.example/pub/fedora/linux/releases/$releasever/Everything/source/tree/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-source-$releasever&arch=$basearch
enabled=0
metadata_expire=7d
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False
1 Like

this should be commented out. Here’s mine for comparison:

[fedora]
name=Fedora $releasever - $basearch
#baseurl=http://download.example/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch
enabled=1
countme=1
metadata_expire=7d
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[fedora-debuginfo]
name=Fedora $releasever - $basearch - Debug
#baseurl=http://download.example/pub/fedora/linux/releases/$releasever/Everything/$basearch/debug/tree/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-$releasever&arch=$basearch
enabled=0
metadata_expire=7d
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[fedora-source]
name=Fedora $releasever - Source
#baseurl=http://download.example/pub/fedora/linux/releases/$releasever/Everything/source/tree/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-source-$releasever&arch=$basearch
enabled=0
metadata_expire=7d
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

I think it looks OK apart from that. Could you comment it out and see if that changes anything?

1 Like

After commenting-out those two lines, my own fedora.repo looks identical to yours.

However this is what I get back when I tried:

sudo dnf install nordvpn-3.14.0-1.x86_64.rpm

Fedora 36 - x86_64 0.0 B/s | 0 B 06:00
Errors during downloading metadata for repository ‘fedora’:

Similarly pasting anything starting with mirrors.fedoraproject.org into my browser address bar comes back:

This connection has timed out

I pinged mirrors.fedoraproject.org from a RaspberryPi and from Fedora34 (a Qubes VM on my laptop). Both of these DO get a response.

I have never seen a problem like this before. My Fedora36-desktop is selectively ignoring mirrors.fedoraproject.org.

All devices access the same Internet account and have the same IP address. The desktop is a cable connection to the modem-router, the Pi and laptop are WiFi.

I have a few school projects going on which access port 3000 & ports 8080 - 8086. These projects are closed right now. Could this have anything to do with blocking access to mirrors.fedoraproject.org?

1 Like

I live in southeastern Colorado, and ping has no trouble finding mirrors.fedoraproject.org. If this hasn’t cleared up, try using traceroute instead to see how far the pings are getting.

Are you sure something hasn’t changed in your network settings firewall selinux router.Can you surf the internet and have you checked fedora’s mirror sites to see if one works.

@sideburns This is the traceroute print-out.

Leaves Canada, gets close (80.239.128.180) then turns away from Chicago, goes to New York, then London then peters out.

traceroute to mirrors.fedoraproject.org (80.239.156.215), 30 hops max, 60 byte packets
1 _gateway (10.0.0.1) 2.109 ms 2.290 ms 2.553 ms
2 24.77.128.1 (24.77.128.1) 18.900 ms 18.912 ms 18.896 ms
3 rc2nr-be107-1.wp.shawcable.net (64.59.180.101) 19.376 ms 19.365 ms 19.380 ms
4 24.244.62.21 (24.244.62.21) 19.253 ms 19.247 ms 19.255 ms
5 24.244.61.217 (24.244.61.217) 19.454 ms 19.455 ms 19.455 ms
6 rc2nr-be1.wp.shawcable.net (24.244.58.157) 19.225 ms 16.090 ms 16.073 ms
7 rc3sc-be26.wp.shawcable.net (66.163.73.145) 16.049 ms 9.447 ms 15.179 ms
8 rc4ec-be25-1.il.shawcable.net (66.163.75.134) 30.168 ms 25.361 ms 31.800 ms
9 rc3ec-be6-1.il.shawcable.net (66.163.65.69) 33.780 ms 33.471 ms 31.629 ms
10 chi-b23-link.ip.twelve99.net (80.239.128.180) 63.427 ms 63.338 ms 63.341 ms
11 nyk-bb2-link.ip.twelve99.net (62.115.137.58) 80.024 ms 79.623 ms 80.063 ms
12 ldn-bb1-link.ip.twelve99.net (62.115.113.21) 153.322 ms 153.180 ms *
13 prs-bb1-link.ip.twelve99.net (62.115.135.25) 158.723 ms 160.058 ms 156.275 ms
14 ffm-bb1-link.ip.twelve99.net (62.115.123.12) 162.609 ms 162.544 ms *
15 * * *
16 * * *
17 * * *

Try to flush the DNS-cache like:
resolvectl flush-caches

then the first thing after:
sudo dnf upgrade --refresh

2 Likes

If @ilikelinux’s suggestion doesn’t help, try the traceroute again and see if it’s stalling at the same point. If so, the problem is between them and what should be the next hop, and you may need to ask the technical contact at twelve99.net for help.

2 Likes

@ilikelinux’s idea did not work.

@straycat. I don’t see anything that specifically relates to mirrors or fedoraproject or any IP address.

For ports and services, should something be listed for “mirrors”, and if so what is it called? Any particular ports that should be open?

I tried accessing “mirrors.fedoraproject.org” with four different browsers on Fedora36; only Tor got through.

This re-directs to “Home - MirrorManager

When I paste this into the address bar of the other three browsers, the site is reachable from Fedora36.

In the firewall, Tor is listed as “tor-socks” in the Fedora Workstation services area. I do not see a listing for any other browsers.

libvirt has this: rich rules: rule priority=“32767” reject. Is this significant?

I am suspicious that it is a firewall issue; it could be rejecting the re-direct except for Tor for some reason.

That sounds like a DNS issue.

nslookup mirrors.fedoraproject.org
dig mirrors.fedoraproject.org
dig mirrors.fedoraproject.org @8.8.8.8

Have you checked

resolvectl status
resolvectl query mirrors.fedoraproject.org

and

systemctl status systemd-resolved.service

?

1 Like

@augenauf

Results of your recommended queries:

Server:		127.0.0.53
Address:	127.0.0.53#53

Name:	mirrors.fedoraproject.org
Address: 80.239.156.215
; <<>> DiG 9.16.28-RH <<>> mirrors.fedoraproject.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58521
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;mirrors.fedoraproject.org.	IN	A

;; ANSWER SECTION:
mirrors.fedoraproject.org. 0	IN	A	80.239.156.215

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Jun 09 08:19:00 CDT 2022
;; MSG SIZE  rcvd: 70
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31545
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mirrors.fedoraproject.org.	IN	A

;; ANSWER SECTION:
mirrors.fedoraproject.org. 295	IN	CNAME	wildcard.fedoraproject.org.
wildcard.fedoraproject.org. 55	IN	A	140.211.169.196
wildcard.fedoraproject.org. 55	IN	A	8.43.85.73
wildcard.fedoraproject.org. 55	IN	A	8.43.85.67
wildcard.fedoraproject.org. 55	IN	A	67.219.144.68
wildcard.fedoraproject.org. 55	IN	A	152.19.134.198
wildcard.fedoraproject.org. 55	IN	A	209.132.190.2
wildcard.fedoraproject.org. 55	IN	A	152.19.134.142
wildcard.fedoraproject.org. 55	IN	A	35.81.0.97
wildcard.fedoraproject.org. 55	IN	A	38.145.60.20
wildcard.fedoraproject.org. 55	IN	A	38.145.60.21

;; Query time: 35 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jun 09 08:21:50 CDT 2022
;; MSG SIZE  rcvd: 237
  • resolvectl status
Global
       Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp5s0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 64.59.176.13
       DNS Servers: 64.59.176.13 64.59.177.226 2001:4e8:0:4002::14
                    2001:4e8:0:4012::14
        DNS Domain: wp.shawcable.net

Link 3 (virbr0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
mirrors.fedoraproject.org: 80.239.156.215

-- Information acquired via protocol DNS in 785us.
-- Data is authenticated: yes; Data was acquired via local or encrypted transport: yes
-- Data from: synthetic
  • systemctl status systemd-resolved.service
systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled;>
     Active: active (running) since Tue 2022-06-07 18:16:40 CDT; 1 day 14h ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network->
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>
   Main PID: 815 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 9403)
     Memory: 3.7M
        CPU: 14.007s
     CGroup: /system.slice/systemd-resolved.service
             └─ 815 /usr/lib/systemd/systemd-resolved

Jun 07 18:16:40 fedora-main-drive systemd-resolved[815]: Positive Trust Anchors:
Jun 07 18:16:40 fedora-main-drive systemd-resolved[815]: . IN DS 20326 8 2 e06d>
Jun 07 18:16:40 fedora-main-drive systemd-resolved[815]: Negative trust anchors>
Jun 07 18:16:40 fedora-main-drive systemd-resolved[815]: Using system hostname >
Jun 07 18:16:40 fedora-main-drive systemd[1]: Started systemd-resolved.service >
Jun 07 18:17:24 fedora-main-drive systemd-resolved[815]: enp5s0: Bus client set>
Jun 07 18:17:24 fedora-main-drive systemd-resolved[815]: enp5s0: Bus client set>
Jun 07 18:17:24 fedora-main-drive systemd-resolved[815]: enp5s0: Bus client set>
Jun 07 18:17:25 fedora-main-drive systemd-resolved[815]: enp5s0: Bus client set>
Jun 08 23:28:22 fedora-main-drive systemd-resolved[815]: Flushed all caches.
lines 1-25/25 (END)

DNS resolution is working fine, so that is not the issue.

I also noted, traceroute to mirrors.fedoraproject.org would have failed if DNS was broken.

I think this could be a routing issue caused by twelve99.net. Why would they route you from chicago to NY to London to Paris to Frankfurt and then to nowhere…?

1 Like

I haven’t used tor in years but I know it bounces all over the world finding servers that can’t be traced back to your ip.If one of those servers is no longer working it will fail until you reset the tor settings.You might try to disable your firewall and try fedora again and if it works you will know where to trouble shoot by removing whatever is blocking you.

1 Like

I dont think above traceroute was done using tor network

1 Like

The traceroute was with Firefox, not Tor.

Tor is the ONLY browser on my desktop that can connect with the mirror site without help.

Firefox, Vivaldi, Google Chrome, all fail unless…

I opened a (free) tunnelbear (vpn) account; when the VPN is active (IP address is somewhere in the USA, not Canada) the browsers are able to connect.

Ping still does not work.

I am going to go through the firewall manual, then disconnect my firewall (temporarily) and see what happens.

disabling the firewall made no difference

I’ll contact twelve99.net

2 Likes