You are not logged in.

#1 2018-08-14 13:56:29

TheGoliath
Member
From: Germany
Registered: 2017-03-24
Posts: 51
Website

[Solved] systemd users aren't created properly

Hello again, guys.
Today I got another problem which may be a part of my systemd network-online.target problem, too.
I'm currently philosophizing about the network-online.target problem (https://bbs.archlinux.org/viewtopic.php?id=239191)
and I thought that it'd be maybe not working cause of the lack of the systemd-users. So basically I had to add all the users manually
so my systemd-resolved and systemd-networkd were working (adding users systemd-network and systemd-resolve helped a lot).
But still I'm lacking users I think. So my plain new set-up system comes with the following users:
https://imgur.com/a/mny5wkJ
You can also see the the error message I get when trying to start the systemd-resolved again.

Maybe someone can help me out with this (already tried reinstalling systemd but had no luck)

Cheers,
TheGoliath

Last edited by TheGoliath (2018-09-22 19:59:04)

Offline

#2 2018-08-14 14:00:24

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Offline

#3 2018-08-14 14:02:30

TheGoliath
Member
From: Germany
Registered: 2017-03-24
Posts: 51
Website

Re: [Solved] systemd users aren't created properly

Okay, thanks. But still, why is the resolved service still failing

EDIT.:
I'm currently connect to the server via a vnc console in firefox.
So I'm not able to paste it properly

Last edited by TheGoliath (2018-08-14 14:04:16)

Offline

#4 2018-08-14 14:04:49

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: [Solved] systemd users aren't created properly

Post the actual text of the error message.  Look back through the journal and post the output from the failure before you created systemd-resolved.
Edit:
List_of_applications#Pastebin_clients tip box covers how to post from the console.

Last edited by loqs (2018-08-14 14:06:30)

Offline

#5 2018-08-14 16:10:42

TheGoliath
Member
From: Germany
Registered: 2017-03-24
Posts: 51
Website

Re: [Solved] systemd users aren't created properly

One thing. The systemd-sysusers.service is up and running. Even if I invoke

sudo systemd-sysusers

It doesn't change anything. systemd-resolve is still whining. But it normally should.
(How to reproduce:
Get yourself a pc or vm and pacstrap arch.
Reboot system after proper config and installation.
You'll see, that (if systemd-resolved is enabled) it won't come up)

Offline

#6 2018-08-14 16:17:53

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: [Solved] systemd users aren't created properly

What is the actual output of `systemctl status systemd-sysusers.service` ?  https://bbs.archlinux.org/viewtopic.php?id=57855
If the system does not have network access redirect the output to a file, copy the file to removable media or a shared filesystem and post the file contents from a system with a network connection.

Offline

#7 2018-08-14 16:23:31

TheGoliath
Member
From: Germany
Registered: 2017-03-24
Posts: 51
Website

Re: [Solved] systemd users aren't created properly

[root@Eggy ~]# systemctl status systemd-resolved systemd-sysusers
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2018-08-14 16:20:23 UTC; 9s ago
     Docs: man:systemd-resolved.service(8)
           [url]https://www.freedesktop.org/wiki/Software/systemd/resolved[/url]
           [url]https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers[/url]
           [url]https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients[/url]
  Process: 1104 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=1/FAILURE)
 Main PID: 1104 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

Aug 14 16:20:23 Eggy systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 16:20:23 Eggy systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 14 16:20:23 Eggy systemd[1]: Failed to start Network Name Resolution.
Aug 14 16:20:23 Eggy systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Aug 14 16:20:23 Eggy systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5.
Aug 14 16:20:23 Eggy systemd[1]: Stopped Network Name Resolution.
Aug 14 16:20:23 Eggy systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 14 16:20:23 Eggy systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 14 16:20:23 Eggy systemd[1]: Failed to start Network Name Resolution.

● systemd-sysusers.service - Create System Users
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static; vendor preset: disabled)
   Active: inactive (dead)
Condition: start condition failed at Tue 2018-08-14 16:14:06 UTC; 6min ago
     Docs: man:sysusers.d(5)
           man:systemd-sysusers.service(8)
[root@Eggy ~]# cat /usr/lib/systemd/system/systemd-sysusers.service 
#  SPDX-License-Identifier: LGPL-2.1+
#
#  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=Create System Users
Documentation=man:sysusers.d(5) man:systemd-sysusers.service(8)
DefaultDependencies=no
Conflicts=shutdown.target
After=systemd-remount-fs.service
Before=sysinit.target shutdown.target systemd-update-done.service
ConditionNeedsUpdate=/etc

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/systemd-sysusers
TimeoutSec=90s

That is the status of systemd-resolved systemd-sysusers + the unit file.

One sec. Could it be that there is a problem with the "NeedsUpdate" condition of /etc?

EDIT.:
After restarting the systemd-sysusers, it comes up but still, the users aren't available

[root@Eggy ~]# sudo systemctl status systemd-sysusers.service 
● systemd-sysusers.service - Create System Users
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static; vendor preset: disabled)
   Active: active (exited) since Tue 2018-08-14 16:46:30 UTC; 27s ago
     Docs: man:sysusers.d(5)
           man:systemd-sysusers.service(8)
  Process: 5704 ExecStart=/usr/bin/systemd-sysusers (code=exited, status=0/SUCCESS)
 Main PID: 5704 (code=exited, status=0/SUCCESS)

Aug 14 16:46:30 Eggy systemd[1]: Starting Create System Users...
Aug 14 16:46:30 Eggy systemd[1]: Started Create System Users.

cheers

Last edited by TheGoliath (2018-08-14 16:48:32)

Offline

#8 2018-08-14 18:40:24

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: [Solved] systemd users aren't created properly

TheGoliath wrote:

After restarting the systemd-sysusers, it comes up but still, the users aren't available

Are you referring to systemd-resolve and systemd-network users?  They are are not created by systemd-sysusers as per my link post #2.

Offline

#9 2018-08-14 21:35:05

Everette88
Member
Registered: 2018-02-17
Posts: 41

Re: [Solved] systemd users aren't created properly

Both systemd-resolved and systemd-networkd are using DynamiUsers, those users shouldn't be in /etc/passwd. Can you show your /etc/nsswitch.conf ?

Offline

#10 2018-08-14 21:56:45

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: [Solved] systemd users aren't created properly

@Everette88 there is already https://bbs.archlinux.org/viewtopic.php?id=239191 for the networking issue.  To avoid this thread being a duplicate please limit its scope to system users.

Offline

#11 2018-08-15 12:01:10

TheGoliath
Member
From: Germany
Registered: 2017-03-24
Posts: 51
Website

Re: [Solved] systemd users aren't created properly

loqs wrote:
TheGoliath wrote:

After restarting the systemd-sysusers, it comes up but still, the users aren't available

Are you referring to systemd-resolve and systemd-network users?  They are are not created by systemd-sysusers as per my link post #2.

Yes. I'm referring to that. If the users aren't neccessary, why are the systemd-networkd and systemd-resolved services failing on a plain arch linux installation?

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files mymachines systemd
group: files mymachines systemd
shadow: files

publickey: files

hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

(The /etc/nsswitch.conf file for further reference)

Offline

#12 2018-08-15 12:06:58

TheGoliath
Member
From: Germany
Registered: 2017-03-24
Posts: 51
Website

Re: [Solved] systemd users aren't created properly

@loqs

#  SPDX-License-Identifier: LGPL-2.1+
#
#  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=https://www.freedesktop.org/wiki/Software/systemd/resolved
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-networkd.service
Before=network.target nss-lookup.target shutdown.target
Conflicts=shutdown.target
Wants=nss-lookup.target

[Service]
Type=notify
Restart=always
RestartSec=0
ExecStart=!!/usr/lib/systemd/systemd-resolved
WatchdogSec=3min
User=systemd-resolve
DynamicUser=yes
CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
PrivateDevices=yes
ProtectHome=yes
ProtectControlGroups=yes
ProtectKernelTunables=yes
ProtectKernelModules=yes
MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictNamespaces=yes
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
SystemCallFilter=@system-service
SystemCallErrorNumber=EPERM
SystemCallArchitectures=native
LockPersonality=yes
RuntimeDirectory=systemd/resolve
RuntimeDirectoryPreserve=yes

[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.resolve1.service

Why is there a systemd-resolve user specified when the DynamicUsers Option is set?

Offline

#13 2018-08-15 16:04:04

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: [Solved] systemd users aren't created properly

TheGoliath wrote:

Why is there a systemd-resolve user specified when the DynamicUsers Option is set?

man 5 systemd.exec wrote:

DynamicUser=
           Takes a boolean parameter. If set, a UNIX user and group pair is
           allocated dynamically when the unit is started, and released as
           soon as it is stopped. The user and group will not be added to
           /etc/passwd or /etc/group, but are managed transiently during
           runtime. The nss-systemd(8) glibc NSS module provides integration
           of these dynamic users/groups into the system's user and group
           databases. The user and group name to use may be configured via
           User= and Group= (see above).

Edit:
The system will not have systemd-resolve and systemd-network users if the services are not active such as because they have failed.
Edit2:
Please post the journal from a boot with the option systemd.log_level=debug

Last edited by loqs (2018-08-15 16:56:13)

Offline

#14 2018-08-16 19:15:23

TheGoliath
Member
From: Germany
Registered: 2017-03-24
Posts: 51
Website

Re: [Solved] systemd users aren't created properly

Aug 14 15:27:33 Eggy systemd-networkd[326]: /etc/systemd/network/20-wired.network:7: Unknown lvalue 'UseDomains' in section 'Network'
Aug 14 15:27:33 Eggy systemd-networkd[326]: containerbr0: netdev ready
Aug 14 15:27:33 Eggy systemd-networkd[326]: Enumeration completed
Aug 14 15:27:33 Eggy systemd[1]: Started Network Service.
Aug 14 15:27:33 Eggy systemd-networkd[326]: lo: Link is not managed by us
Aug 14 15:27:33 Eggy systemd-networkd[326]: containerbr0: Link is not managed by us
Aug 14 15:27:33 Eggy systemd-udevd[353]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 14 15:27:33 Eggy systemd[1]: Starting Wait for Network to be Configured...
Aug 14 15:27:33 Eggy systemd[1]: Starting Network Name Resolution...
Aug 14 15:27:33 Eggy systemd-networkd[326]: ens3: Gained carrier
Aug 14 15:27:33 Eggy systemd-networkd-wait-online[355]: ignoring: containerbr0
Aug 14 15:27:33 Eggy systemd-networkd[326]: lo: Link is not managed by us
Aug 14 15:27:33 Eggy systemd-networkd-wait-online[355]: ignoring: containerbr0
Aug 14 15:27:33 Eggy systemd-networkd[326]: request_name_destroy_callback n_ref=2
Aug 14 15:27:33 Eggy kernel: IPv6: ADDRCONF(NETDEV_UP): containerbr0: link is not ready
Aug 14 15:27:33 Eggy dbus-daemon[314]: Unknown username "systemd-resolve" in message bus configuration file
Aug 14 15:27:33 Eggy dbus-daemon[314]: [system] Reloaded configuration
Aug 14 15:27:33 Eggy systemd-networkd[326]: request_name_destroy_callback n_ref=1
Aug 14 15:27:33 Eggy systemd-networkd-wait-online[355]: ignoring: containerbr0
Aug 14 15:27:33 Eggy systemd-networkd-wait-online[355]: ignoring: containerbr0
Aug 14 15:27:33 Eggy systemd-networkd-wait-online[355]: ignoring: containerbr0
Aug 14 15:27:33 Eggy systemd-networkd[326]: ens3: DHCPv4 address IPAddrRedacted/22 via IPAddrRedacted
Aug 14 15:27:33 Eggy systemd-timesyncd[307]: Network configuration changed, trying to establish connection.
Aug 14 15:27:33 Eggy systemd-networkd-wait-online[355]: ignoring: containerbr0
Aug 14 15:27:33 Eggy dbus-daemon[314]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=63822 pid=326 comm="/usr/lib/systemd/systemd-networkd ")
Aug 14 15:27:33 Eggy systemd[1]: Starting Hostname Service...
Aug 14 15:27:33 Eggy systemd-swap[315]: INFO: Zswap: backup current configuration: complete
Aug 14 15:27:33 Eggy systemd-swap[315]: INFO: Zswap: set new parameters: start
Aug 14 15:27:33 Eggy systemd-swap[315]: INFO: Zswap: Enable: 1, Comp: lz4,  Max pool %: 25, Zpool: zbud
Aug 14 15:27:33 Eggy systemd-swap[315]: INFO: Zswap: set new parameters: complete
Aug 14 15:27:33 Eggy systemd-swap[315]: INFO: swapD: pickup devices from systemd-gpt-auto-generator
Aug 14 15:27:33 Eggy ssh-keygen[318]: ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
Aug 14 15:27:33 Eggy systemd[1]: Started SSH Key Generation.
Aug 14 15:27:33 Eggy dbus-daemon[314]: [system] Successfully activated service 'org.freedesktop.hostname1'
Aug 14 15:27:33 Eggy systemd[1]: Started Hostname Service.
Aug 14 15:27:33 Eggy dbus-daemon[314]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.10' (uid=0 pid=363 comm="/usr/lib/systemd/systemd-hostnamed ")
Aug 14 15:27:33 Eggy systemd[1]: Starting Authorization Manager...
Aug 14 15:27:33 Eggy systemd-swap[315]: INFO: swapD: searching swap devices
Aug 14 15:27:33 Eggy systemd-resolved[356]: Cannot resolve user name systemd-resolve: No such process
Aug 14 15:27:33 Eggy systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 15:27:33 Eggy systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 14 15:27:33 Eggy systemd[1]: Failed to start Network Name Resolution.
Aug 14 15:27:33 Eggy systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Aug 14 15:27:33 Eggy systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
Aug 14 15:27:33 Eggy systemd[1]: Stopped Network Name Resolution.
Aug 14 15:27:33 Eggy systemd[1]: Starting Network Name Resolution...
Aug 14 15:27:33 Eggy polkitd[397]: Started polkitd version 0.114
Aug 14 15:27:33 Eggy polkitd[397]: Loading rules from directory /etc/polkit-1/rules.d
Aug 14 15:27:33 Eggy polkitd[397]: Loading rules from directory /usr/share/polkit-1/rules.d
Aug 14 15:27:33 Eggy polkitd[397]: Finished loading, compiling and executing 2 rules
Aug 14 15:27:33 Eggy dbus-daemon[314]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Aug 14 15:27:33 Eggy systemd[1]: Started Authorization Manager.
Aug 14 15:27:33 Eggy polkitd[397]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Aug 14 15:27:33 Eggy systemd-hostnamed[363]: Changed host name to 'myfancyhostnameidontwanttoshow.life'
Aug 14 15:27:33 Eggy systemd-resolved[404]: Cannot resolve user name systemd-resolve: No such process
Aug 14 15:27:33 Eggy systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 15:27:33 Eggy systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 14 15:27:33 Eggy systemd[1]: Failed to start Network Name Resolution.
Aug 14 15:27:33 Eggy systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Aug 14 15:27:33 Eggy systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2.
Aug 14 15:27:33 Eggy systemd[1]: Stopped Network Name Resolution.

An excerpt of my boot (with the systemd.log_level=debug flag enabled)

Cheers

Last edited by TheGoliath (2018-08-16 19:16:53)

Offline

#15 2018-08-16 19:24:21

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: [Solved] systemd users aren't created properly

Offline

#16 2018-08-17 13:08:40

TheGoliath
Member
From: Germany
Registered: 2017-03-24
Posts: 51
Website

Re: [Solved] systemd users aren't created properly

Solved. Seems to be the issue.
Thanks^^

Offline

Board footer

Powered by FluxBB