Re: Curl Errors During DNF Repository Refresh

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 22/11/24 13:55, Jonathan Billings wrote:
On Nov 21, 2024, at 16:06, Stephen Morris <steve.morris.au@xxxxxxxxx> wrote:
    Can someone tell me if the following errors were because of a network hiccup (there was no visual indication from F41 that the wifi network had disconnected and reconnected) or whether it was because of some other reason?
    Running the command dnf check-upgrade again indicated there was nothing to do.

Docker CE Stable - x86_64                                                                                                                        ???% |   0.0   B/s |   0.0   B |  00m00s
>>> Curl error (6): Could not resolve hostname for https://download.docker.com/linux/fedora/41/x86_64/stable/repodata/repomd.xml [Could not resolve host: download.docker.com] - https://d
[ SNIP]

My hunch is that it couldn’t resolve the host name for the repo.

But seriously, was there something about these errors or other effects that made you think it was something other than DNS being broken?
I would have thought that if my wifi connection had been temporarily disconnected, hence the data couldn't be retrieved, I would have gotten popups from fedora around the disconnect/reconnect.
I would have also thought that if it was a broken DNS the reissuing the dnf check-upgrade would have repeated the messages.
With the reissuing of the command not producing any messages about refreshing the repositories in question and saying there were updates to put on, it had refreshed the repositories even though it got the error, and there were actually no updates?

regards,
Steve


-- 
Jonathan Billings


Attachment: OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux