Sorry... Getting confused in my old age... s/33/32/g s/34/33/g Got my revs out of sink. Problem is still real. Trying the trick of beating NetworkManager into submission with "dns=none" I pulled off this list. Thanks! Regards, Mike On Sat, 2021-01-02 at 17:30 -0500, Michael H. Warfield wrote: > I'm not even sure what to file a bug against. This makes no sense to > me. > > I have four Raspberry Pi's on Fedora 34. One RPi4 and Three RPi3s, > all > running aarch 64. I also have numerous other RPi's on Fedora 33 > aarch64 that are running just fine, parallel configurations. I'm not > upgrading any of my X86_64 systems until I know the root cause of > this. > > If the Fedora 34 systems are up more than a day and I go to update I > get things like this... > > -- > rror: Curl error (6): Couldn't resolve host name for > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > [Could not resolve host: mirrors.fedoraproject.org] ( > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > ). > error: Curl error (6): Couldn't resolve host name for > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > [Could not resolve host: mirrors.fedoraproject.org] ( > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > ). > error: Curl error (6): Couldn't resolve host name for > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > [Could not resolve host: mirrors.fedoraproject.org] ( > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > ). > error: Curl error (6): Couldn't resolve host name for > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > [Could not resolve host: mirrors.fedoraproject.org] ( > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > ). > error: Curl error (6): Couldn't resolve host name for > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > [Could not resolve host: mirrors.fedoraproject.org] ( > https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64 > ). > -- > > And this... > > -- > [mhw@rpi-plate ~]$ host mirrors.fedoraproject.org > mirrors.fedoraproject.org is an alias for wildcard.fedoraproject.org. > wildcard.fedoraproject.org has address 152.19.134.198 > wildcard.fedoraproject.org has address 8.43.85.67 > wildcard.fedoraproject.org has address 209.132.190.2 > wildcard.fedoraproject.org has address 152.19.134.142 > wildcard.fedoraproject.org has address 140.211.169.206 > wildcard.fedoraproject.org has address 8.43.85.73 > wildcard.fedoraproject.org has address 38.145.60.20 > wildcard.fedoraproject.org has address 38.145.60.21 > wildcard.fedoraproject.org has address 140.211.169.196 > wildcard.fedoraproject.org has address 67.219.144.68 > wildcard.fedoraproject.org has IPv6 address > 2620:52:3:1:dead:beef:cafe:fed6 > wildcard.fedoraproject.org has IPv6 address > 2604:1580:fe00:0:dead:beef:cafe:fed1 > wildcard.fedoraproject.org has IPv6 address > 2605:bc80:3010:600:dead:beef:cafe:fed9 > wildcard.fedoraproject.org has IPv6 address > 2620:52:3:1:dead:beef:cafe:fed7 > wildcard.fedoraproject.org has IPv6 address > 2610:28:3090:3001:dead:beef:cafe:fed3 > wildcard.fedoraproject.org has IPv6 address > 2605:bc80:3010:600:dead:beef:cafe:feda > [mhw@rpi-plate ~]$ ping mirrors.fedoraproject.org > ping: mirrors.fedoraproject.org: Name or service not known > [mhw@rpi-plate ~]$ ping6 mirrors.fedoraproject.org > ping6: mirrors.fedoraproject.org: Name or service not known > > -- > > Checking /etc/resolv.conf looks good (host works) and nsswitch.conf > looks good. Doesn't seem to depend on whether I use static name > servers or dhcp served name servers (I have some of each on both the > Fedora 34 and the Fedora 33). All on the same network. All with the > same name servers for resolution. > > /etc/resolv.conf > -- > # Generated by NetworkManager > search wittsend.com > nameserver 8.8.8.8 > nameserver 1.1.1.1 > nameserver 10.205.38.3 > -- > > Restarting NetworkManager - no help > > Rebooting the system restores normal operation for anywhere from > several hours to a day before it happens again. > > WTH changed between 33 and 34 to create this problem? Anybody got > any > suggestions where to look? None, I mean not a single solitary one of > my Fedora 33 systems, x86_64, arm7l (RPi 2's), or aarch64's are > behaving this way but all 4 of my Fedora 34 systems are. > > Regards, > Mike -- Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 | mhw@xxxxxxxxxxxx /\/\|=mhw=|\/\/ | (c) +1 678 463-0932 | http://www.wittsend.com/mhw/ ARIN whois: MHW9-ARIN | An optimist believes we live in the best of all PGP Key: 0xC0EB9675674627FF | possible worlds. A pessimist is sure of it!
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 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
