Re: Curl Errors During DNF Repository Refresh

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

 



On 23/11/24 16:36, Tim wrote:
Jonathan Billings:
But seriously, was there something about these errors or other
effects that made you think it was something other than DNS being
broken?
Stephen Morris:
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.
You could get unable to resolve hostnames due to a networking problem
with your system, your router, your ISP, the route to the host, the
host itself...

But the messages showing that various different domain names couldn't
be resolved virtually discounts its being the end host (unless they all
happened to be on the same server, but I seriously doubt that).

There's every chance you struck a moment while your ISP was fiddling
with things, or something failed there.

I would have also thought that if it was a broken DNS the reissuing
the dnf check-upgrade would have repeated the messages.
I don't see anything regarding that in your log (you mentioned it, but
didn't show any logs).

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?
We can only guess that cached results were used.

Unfortunately you haven't shown us anything else to diagnose the
problem.  Such as using the dig tool on those and other addresses.  The
output of ifconfig, or other commands, showing the network parameters. 
Was there a gateway, a DNS server, did you get a real IP address?  Nor
did you tell us whether anything else was working at the same time (web
browsing, etc).
 
In the past when I have lost internet access because my wifi disconnected from the router and reconnected, I get a popup message from Fedora that the wifi disconnected followed immediately by a popup message saying it had reconnected. That didn't happen in this case.
If there was upstream interference preventing the refreshing of the indicated repositories then I would have expected the reissue of the command to refresh those repositories which it didn't, unless dnf had marked them as refreshed even though they weren't.
I also thought I didn't need to show the messages "Updating and loading repositories" and "Repositories loaded" with nothing in between to show that the messages are produced even if there is nothing to do. I'll know better next time.
By default Fedora is configured to get DNS servers from DHCP, which I haven't changed, and DHCP is configured in my router to get those addresses from my ISP, with my router as the gateway.
It is possible my router/modem were playing up, as afterwards I was having issues with maintaining internet connections in Windows while playing a steam game, which restarting the modem and router rectified.
But if the repositories in question were not actually refreshed as the error messages were indicating, why did a reissue of the command not refresh them, had DNF invalidly marked them as refreshed when they actually weren't, or were the error messages bogus, or did DNF retry after producing the messages and not told us it had successfully refreshed the repositories?

regards,
Steve

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