systemd-resolved.service fails

English Network/Internet
1

Operating System: openSUSE Tumbleweed 20220221
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.10-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

Form journal:

**notebook:~ #** journalctl -b -u systemd-resolved.service --no-hostname --no-pager 
Feb 23 06:33:00 systemd[1]: Starting Network Name Resolution... 
Feb 23 06:33:00 systemd[5351]: **systemd-resolved.service: Failed to determine user credentials: No such process**
Feb 23 06:33:00 systemd[5351]: **systemd-resolved.service: Failed at step USER spawning /usr/lib/systemd/systemd-resolved: No such process**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Main process exited, code=exited, status=217/USER**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Failed with result 'exit-code'.**
Feb 23 06:33:00 systemd[1]: **Failed to start Network Name Resolution.**
Feb 23 06:33:00 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1. 
Feb 23 06:33:00 systemd[1]: Stopped Network Name Resolution. 
Feb 23 06:33:00 systemd[1]: Starting Network Name Resolution... 
Feb 23 06:33:00 systemd[5356]: **systemd-resolved.service: Failed to determine user credentials: No such process**
Feb 23 06:33:00 systemd[5356]: **systemd-resolved.service: Failed at step USER spawning /usr/lib/systemd/systemd-resolved: No such process**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Main process exited, code=exited, status=217/USER**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Failed with result 'exit-code'.**
Feb 23 06:33:00 systemd[1]: **Failed to start Network Name Resolution.**
Feb 23 06:33:00 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2. 
Feb 23 06:33:00 systemd[1]: Stopped Network Name Resolution. 
Feb 23 06:33:00 systemd[1]: Starting Network Name Resolution... 
Feb 23 06:33:00 systemd[5359]: **systemd-resolved.service: Failed to determine user credentials: No such process**
Feb 23 06:33:00 systemd[5359]: **systemd-resolved.service: Failed at step USER spawning /usr/lib/systemd/systemd-resolved: No such process**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Main process exited, code=exited, status=217/USER**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Failed with result 'exit-code'.**
Feb 23 06:33:00 systemd[1]: **Failed to start Network Name Resolution.**
Feb 23 06:33:00 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 3. 
Feb 23 06:33:00 systemd[1]: Stopped Network Name Resolution. 
Feb 23 06:33:00 systemd[1]: Starting Network Name Resolution... 
Feb 23 06:33:00 systemd[5362]: **systemd-resolved.service: Failed to determine user credentials: No such process**
Feb 23 06:33:00 systemd[5362]: **systemd-resolved.service: Failed at step USER spawning /usr/lib/systemd/systemd-resolved: No such process**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Main process exited, code=exited, status=217/USER**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Failed with result 'exit-code'.**
Feb 23 06:33:00 systemd[1]: **Failed to start Network Name Resolution.**
Feb 23 06:33:00 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 4. 
Feb 23 06:33:00 systemd[1]: Stopped Network Name Resolution. 
Feb 23 06:33:00 systemd[1]: Starting Network Name Resolution... 
Feb 23 06:33:00 systemd[5365]: **systemd-resolved.service: Failed to determine user credentials: No such process**
Feb 23 06:33:00 systemd[5365]: **systemd-resolved.service: Failed at step USER spawning /usr/lib/systemd/systemd-resolved: No such process**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Main process exited, code=exited, status=217/USER**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Failed with result 'exit-code'.**
Feb 23 06:33:00 systemd[1]: **Failed to start Network Name Resolution.**
Feb 23 06:33:00 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. 
Feb 23 06:33:00 systemd[1]: Stopped Network Name Resolution. 
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Start request repeated too quickly.**
Feb 23 06:33:00 systemd[1]: **systemd-resolved.service: Failed with result 'exit-code'.**
Feb 23 06:33:00 systemd[1]: **Failed to start Network Name Resolution.**
**notebook:~ #**

Any idea?

2

systemd-resolved.service works properly on another machine:

Operating System: openSUSE Tumbleweed 20220221
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.10-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics
Memory: 29.3 GiB of RAM
Graphics Processor: AMD Radeon Vega 11 Graphics

**erlangen:~ #** journalctl -b -u systemd-resolved.service --no-hostname --no-pager 
Feb 22 19:36:34 systemd[1]: Starting Network Name Resolution... 
Feb 22 19:36:34 systemd-resolved[740]: Positive Trust Anchors: 
Feb 22 19:36:34 systemd-resolved[740]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d 
Feb 22 19:36:34 systemd-resolved[740]: Negative trust anchors: home.arpa 10.in-addr.arpa ...
Feb 22 19:36:34 systemd-resolved[740]: Using system hostname 'erlangen'. 
Feb 22 19:36:34 systemd[1]: Started Network Name Resolution. 
Feb 23 07:03:52 systemd-resolved[740]: Clock change detected. Flushing caches. 
**erlangen:~ #**
3

What exactly is not clear in

Feb 23 06:33:00 systemd[5351]: **systemd-resolved.service: Failed to determine user credentials: No such process**

You are the systemd expert, you should know how to read service definition and check whether required user exists.

4 
**notebook:~ #** cat /usr/lib/sysusers.d/systemd-resolve.conf  
#  This file is part of systemd. 
# 
#  systemd is free software; you can redistribute it and/or modify it 
#  under the terms of the GNU Lesser General Public License as published by 
#  the Free Software Foundation; either version 2.1 of the License, or 
#  (at your option) any later version. 

u systemd-resolve - "systemd Resolver" 
**notebook:~ #**

Contents and permissions are identical on failing host “notebook” and working host “erlangen”.:frowning:

5

Did this just happen following a TW update?

6

https://bugzilla.opensuse.org/show_bug.cgi?id=1196322

7

erlangen was duped and works. notebook is a new install and fails.

8

Can you share the systemd unit file?

9

Sure. It’s unmodified:

**# /usr/lib/systemd/system/systemd-resolved.service**
#  SPDX-License-Identifier: LGPL-2.1-or-later 
# 
#  This file is part of systemd. 
# 
#  systemd is free software; you can redistribute it and/or modify it 
#  under the terms of the GNU Lesser General Public License as published by 
#  the Free Software Foundation; either version 2.1 of the License, or 
#  (at your option) any later version. 

[Unit] 
Description=Network Name Resolution 
Documentation=man:systemd-resolved.service(8) 
Documentation=man:org.freedesktop.resolve1(5) 
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers 
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients 

DefaultDependencies=no 
After=systemd-sysusers.service systemd-networkd.service 
Before=network.target nss-lookup.target shutdown.target 
Conflicts=shutdown.target 
Wants=nss-lookup.target 

[Service] 
AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE 
BusName=org.freedesktop.resolve1 
CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE 
ExecStart=!!/usr/lib/systemd/systemd-resolved 
LockPersonality=yes 
MemoryDenyWriteExecute=yes 
NoNewPrivileges=yes 
PrivateDevices=yes 
PrivateTmp=yes 
ProtectProc=invisible 
ProtectClock=yes 
ProtectControlGroups=yes 
ProtectHome=yes 
ProtectKernelLogs=yes 
ProtectKernelModules=yes 
ProtectKernelTunables=yes 
ProtectSystem=strict 
Restart=always 
RestartSec=0 
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 
RestrictNamespaces=yes 
RestrictRealtime=yes 
RestrictSUIDSGID=yes 
RuntimeDirectory=systemd/resolve 
RuntimeDirectoryPreserve=yes 
SystemCallArchitectures=native 
SystemCallErrorNumber=EPERM 
SystemCallFilter=@system-service 
Type=notify 
User=systemd-resolve 
WatchdogSec=3min 

[Install] 
WantedBy=multi-user.target 
Alias=dbus-org.freedesktop.resolve1.service 
**notebook:~ #**
10

Yet another bug report with zero information. Yes, doing actual troubleshooting is more involving than posting random internet links and showing successful logs from your system.

And why you post it here and not in bug report? How are maintainers supposed to guess it?

11

Your comment is both inaccurate and inappropriate.

12

hello,

The error shows a credential error.
In /etc/passwd I have the following users for systemd-*

hpprol2:/etc # grep systemd passwd
systemd-coredump:x:466:466:systemd Core Dumper:/:/usr/sbin/nologin
systemd-network:x:469:469:systemd Network Management:/:/usr/sbin/nologin
systemd-resolve:x:468:468:systemd Resolver:/:/usr/sbin/nologin
systemd-timesync:x:467:467:systemd Time Synchronization:/:/usr/sbin/nologin

Do you have the system user systemd-resolve?

Regards
Philippe

13

The red line was missing. Appended it to passwd and got yet another successful log from my system:

**notebook:~ #** journalctl -b -u systemd-resolved.service  
Feb 23 11:48:03 notebook systemd[1]: Starting Network Name Resolution... 
Feb 23 11:48:03 notebook systemd-resolved[685]: Positive Trust Anchors: 
Feb 23 11:48:03 notebook systemd-resolved[685]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d 
Feb 23 11:48:03 notebook systemd-resolved[685]: Negative trust anchors: home.arpa ...
...
Feb 23 11:48:03 notebook systemd-resolved[685]: Using system hostname 'notebook'. 
Feb 23 11:48:03 notebook systemd[1]: Started Network Name Resolution. 
**notebook:~ #**