You are not logged in.

Pages: 1

#1 2023-03-16 03:00:29

Randy McShandy
Member
Registered: 2023-03-16
Posts: 2

[SOLVED] Upgrade to Systemd 253 borks domain resolution

Hi,
I'm encountering an issue upon upgrade to systemd-253.1-* (issue recreated in 1-3 so far) that's immediately resolved upon a retrograde to systemd-252.5-1.
It seems DNS resolution fails in all cases (left 252 with expected behavior, right 253):

[randy@mcshandy ~]$ ping -v www.archlinux.org                                                                                   [randy@mcshandy ~]$ ping -v www.archlinux.org
ping: sock4.fd: 3 (socktype: SOCK_DGRAM), sock6.fd: 4 (socktype: SOCK_DGRAM), hints.ai_family: AF_UNSPEC                        ping: sock4.fd: 3 (socktype: SOCK_DGRAM), sock6.fd: 4 (socktype: SOCK_DGRAM), hints.ai_family: AF_UNSPEC

ai->ai_family: AF_INET, ai->ai_canonname: 'www.archlinux.org'                                                                 | ping: www.archlinux.org: Temporary failure in name resolution
PING www.archlinux.org (95.217.163.246) 56(84) bytes of data.                                                                 <
64 bytes from archlinux.org (95.217.163.246): icmp_seq=1 ttl=50 time=111 ms                                                   <
64 bytes from archlinux.org (95.217.163.246): icmp_seq=2 ttl=50 time=112 ms                                                   <
64 bytes from archlinux.org (95.217.163.246): icmp_seq=3 ttl=50 time=113 ms                                                   <
64 bytes from archlinux.org (95.217.163.246): icmp_seq=4 ttl=50 time=110 ms                                                   <
64 bytes from archlinux.org (95.217.163.246): icmp_seq=5 ttl=50 time=108 ms                                                   <
^C                                                                                                                            <
--- www.archlinux.org ping statistics ---                                                                                     <
5 packets transmitted, 5 received, 0% packet loss, time 4002ms                                                                <
rtt min/avg/max/mdev = 107.964/111.029/113.444/1.819 ms                                                                       <

Also occurs in web browser. All requests time out on resolution errors. The best investigation I've managed to do so far is checking up on systemd-resolved.service, which yields... something:

[randy@mcshandy ~]$ systemctl status systemd-resolved.service                                                                 | [randy@mcshandy ~]$ sudo systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution                                                                            ● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)                                     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Wed 2023-03-15 20:56:32 EDT; 1min 30s ago                                                 |      Active: active (running) since Wed 2023-03-15 20:40:17 EDT; 10min ago
       Docs: man:systemd-resolved.service(8)                                                                                           Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)                                                                                                 man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers                                        https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients                                                      https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 267 (systemd-resolve)                                                                                            |    Main PID: 268 (systemd-resolve)
     Status: "Processing requests..."                                                                                                Status: "Processing requests..."
      Tasks: 1 (limit: 38413)                                                                                                 |       Tasks: 1 (limit: 38414)
     Memory: 7.6M                                                                                                             |      Memory: 8.3M
        CPU: 113ms                                                                                                            |         CPU: 948ms
     CGroup: /system.slice/systemd-resolved.service                                                                                  CGroup: /system.slice/systemd-resolved.service
             └─267 /usr/lib/systemd/systemd-resolved                                                                          |              └─268 /usr/lib/systemd/systemd-resolved
                                                                                                                              >
                                                                                                                              > Mar 15 20:50:25 mcshandy systemd-resolved[268]: Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:25 mcshandy systemd-resolved[268]: Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:28 mcshandy systemd-resolved[268]: Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:28 mcshandy systemd-resolved[268]: Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:30 mcshandy systemd-resolved[268]: Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:30 mcshandy systemd-resolved[268]: Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:34 mcshandy systemd-resolved[268]: Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:34 mcshandy systemd-resolved[268]: Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:39 mcshandy systemd-resolved[268]: Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
                                                                                                                              > Mar 15 20:50:39 mcshandy systemd-resolved[268]: Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
                                                                                                                              >
                                                                                                                              >
                                                                                                                              >
                                                                                                                              >
                                                                                                                              >

Mar 15 20:56:32 mcshandy systemd[1]: Starting Network Name Resolution...                                                      <
Mar 15 20:56:32 mcshandy systemd-resolved[267]: Positive Trust Anchors:                                                       <
Mar 15 20:56:32 mcshandy systemd-resolved[267]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc68345710423>    <
Mar 15 20:56:32 mcshandy systemd-resolved[267]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.>    <
Mar 15 20:56:32 mcshandy systemd-resolved[267]: Using system hostname 'mcshandy'.                                             <
Mar 15 20:56:32 mcshandy systemd[1]: Started Network Name Resolution.                                                         <
Mar 15 20:56:53 mcshandy systemd-resolved[267]: Clock change detected. Flushing caches.                                       <

The using degraded feature set lines on the right continue ad infinitum. Based on final lines of the left side, never starting network name resolution sure seems indicative of not being able to resolve, well, network names.
Other things checked (based on common recommendations) include:

  1. resolvectl status -- no change between versions

  2. networkctl status -- no change between versions

  3. journalctl -- same, but maybe I'm missing something in the verbosity

  4. lspci -- ditto

After this I tried upgrading to 253 and restarting systemd-networkd.service in-place, and the moment this finishes, resolution fails, seemingly indicating the problem originates here. In the same session, I can downgrade back to 252, restart again, and pings start resolving again immediately. Unfortunately, in both versions, systemctl status systemd-networkd.service have near-identical output, the only diffs seem to be in ordering of a couple prints -- race conditions?

System info:

  • Arch x86_64

  • Linux 6.2.6-arch1-1

  • systemd-252.5-1

Quick edit as I type this up -- not just DSN resolution seems affected, but also directly pinging IPs fails with ping: connect: Network is unreachable. I can see at least some Tx/Rx on a dmenu widget active even while networking is down; I assume it's just to the router.
Hoping for further advice in diagnosing just what's causing this, if anyone can provide recommendations.
Thanks.

Last edited by Randy McShandy (2023-03-17 00:37:10)

Offline

#2 2023-03-16 08:13:14

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,358

Re: [SOLVED] Upgrade to Systemd 253 borks domain resolution

https://bbs.archlinux.org/viewtopic.php … 5#p2085455

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2023-03-17 00:36:39

Randy McShandy
Member
Registered: 2023-03-16
Posts: 2

Re: [SOLVED] Upgrade to Systemd 253 borks domain resolution

Thanks! That did the trick. Disappointed in myself for not taking note of the prior post.

Offline

Pages: 1

Board footer

Powered by FluxBB