Arch Linux

sefacs89

Member

Registered: 2019-08-12

Posts: 27

[Solved] Systemd-Sysusers.service suddenly failed

Hello everyone after today update
i get systemd-sysusers.service failed on boot

journalctl | grep systemd-sysusers
Aug 08 02:05:24 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 08 12:34:57 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 08 14:10:37 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 08 18:46:23 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 09 01:28:14 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 09 19:53:40 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 09 21:34:04 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 09 22:00:32 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 10 07:54:54 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 10 13:22:50 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 10 15:24:00 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 11 02:07:55 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 11 02:14:00 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 12 22:59:43 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 13 13:12:31 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 13 16:40:00 archlinux systemd[1]: systemd-sysusers.service: Succeeded.
Aug 14 13:23:50 archlinux systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 13:23:50 archlinux systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Aug 14 13:23:57 archlinux systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 13:23:57 archlinux systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Aug 14 23:52:22 archlinux systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 23:52:22 archlinux systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Aug 14 23:52:29 archlinux systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 23:52:29 archlinux systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Aug 15 11:10:05 archlinux systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Aug 15 11:10:05 archlinux systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Aug 15 11:10:12 archlinux systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Aug 15 11:10:12 archlinux systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.

* 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 Thu 2019-08-15 12:01:24 EEST; 6h ago
     Docs: man:sysusers.d(5)
           man:systemd-sysusers.service(8)

Aug 15 12:01:24 archlinux systemd[1]: Condition check resulted in Create System Users being skipped.

sudo grpck

'sefacs' is a member of the 'video' group in /etc/group but not in /etc/gshadow
'sefacs' is a member of the 'vboxusers' group in /etc/group but not in /etc/gshadow
'sefacs' is a member of the 'mysql' group in /etc/group but not in /etc/gshadow
'sefacs' is a member of the 'clamav' group in /etc/group but not in /etc/gshadow
'sddm' is a member of the 'video' group in /etc/gshadow but not in /etc/group

/etc/group

root:x:0:root
sys:x:3:bin
mem:x:8:
ftp:x:11:
mail:x:12:
log:x:19:
smmsp:x:25:
proc:x:26:polkitd
games:x:50:
lock:x:54:
network:x:90:
floppy:x:94:
scanner:x:96:
power:x:98:sefacs
adm:x:999:daemon
wheel:x:998:sefacs
kmem:x:997:
tty:x:5:
utmp:x:996:
audio:x:995:
disk:x:994:
input:x:993:
kvm:x:992:
lp:x:991:cups
optical:x:990:
render:x:989:
storage:x:988:sefacs
uucp:x:987:
video:x:986:sefacs:sddm
users:x:985:
systemd-journal:x:984:
rfkill:x:983:
bin:x:1:daemon
daemon:x:2:bin
http:x:33:
nobody:x:65534:
dbus:x:81:
systemd-journal-remote:x:982:
systemd-network:x:981:
systemd-resolve:x:980:
systemd-timesync:x:979:
systemd-coredump:x:978:
uuidd:x:68:
avahi:x:977:
colord:x:976:
polkitd:x:102:
usbmux:x:140:
nvidia-persistenced:x:143:
wireshark:x:150:
cups:x:209:
dnsmasq:x:975:
postgres:x:974:
rtkit:x:133:
git:x:973:
vboxusers:x:108:sefacs
mysql:x:1000:sefacs
clamav:x:64:sefacs:root
lightdm:x:971:
sddm:x:970:
locate:x:21:
flatpak:x:969:
geoclue:x:968:
tss:x:967:
brlapi:x:966:
gdm:x:120:
libvirt:x:965:
gluster:x:964:
rpc:x:32:
spamd:x:182:

i reinstall the systemd
and re-boot the machine
any help would be appreciated
thanks everyone

Last edited by sefacs89 (2019-08-16 15:47:15)

loqs

Member

Registered: 2014-03-06

Posts: 19,101

Re: [Solved] Systemd-Sysusers.service suddenly failed

systemctl status systemd-sysusers.service

Does the output from the above contain the following line after start condition failed?

           └─ ConditionNeedsUpdate=/etc was not met

sefacs89

Member

Registered: 2019-08-12

Posts: 27

Re: [Solved] Systemd-Sysusers.service suddenly failed

systemctl status systemd-sysusers.service

Does the output from the above contain the following line after start condition failed?

           └─ ConditionNeedsUpdate=/etc was not met

hello the output after poweroff and power on is as follows

* systemd-sysusers.service - Create System Users
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2019-08-15 22:15:25 EEST; 5min ago
     Docs: man:sysusers.d(5)
           man:systemd-sysusers.service(8)
  Process: 406 ExecStart=/usr/bin/systemd-sysusers (code=exited, status=1/FAILURE)
 Main PID: 406 (code=exited, status=1/FAILURE)

Aug 15 22:15:25 archlinux systemd[1]: Starting Create System Users...
Aug 15 22:15:25 archlinux systemd-sysusers[406]: Failed to write files: Invalid argument
Aug 15 22:15:25 archlinux systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Aug 15 22:15:25 archlinux systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Aug 15 22:15:25 archlinux systemd[1]: Failed to start Create System Users.

thank you very much

loqs

Member

Registered: 2014-03-06

Posts: 19,101

Re: [Solved] Systemd-Sysusers.service suddenly failed

Were the issues detected by grpck and pwck resolved before the reboot?

sefacs89

Member

Registered: 2019-08-12

Posts: 27

Re: [Solved] Systemd-Sysusers.service suddenly failed

Were the issues detected by grpck and pwck resolved before the reboot?

pwck i run the command just right now

specifically

user 'mysql': directory '/home/mysql' does not exist
user 'gdm': directory '/var/lib/gdm' does not exist
pwck: no changes

then i start manually the service
still the same issue the problem is

the first time the systemd on boot cause of not quite command from grub
shows failed
now the systemd on boot shows OK
but still the service doesnt work

if i chroot the computer and then
remove everything from systemd files to group,group,shadow,gshadow file
(if i do a backup first)
will it fixes my problem?

thanks

loqs

Member

Registered: 2014-03-06

Posts: 19,101

Re: [Solved] Systemd-Sysusers.service suddenly failed

If grpck is not resolving the issues detected in post #1 have you tried resolving them with usermod?
Do you know how the inconsistencies could have been created such as by manually editing /etc/group or merging .pacnew files?

sefacs89

Member

Registered: 2019-08-12

Posts: 27

Re: [Solved] Systemd-Sysusers.service suddenly failed

If grpck is not resolving the issues detected in post #1 have you tried resolving them with usermod?
Do you know how the inconsistencies could have been created such as by manually editing /etc/group or merging .pacnew files?

its seems that i have a general and random errors around the groups and users in the system
for example
today first boot

sudo systemctl --failed 
  UNIT           LOAD   ACTIVE SUB    DESCRIPTION                                 
* shadow.service loaded failed failed Verify integrity of password and group files

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

sudo systemctl status shadow.service
* shadow.service - Verify integrity of password and group files
   Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2019-08-16 08:44:58 EEST; 5min ago
  Process: 423 ExecStart=/bin/sh -c /usr/bin/pwck -r || r=1; /usr/bin/grpck -r && exit $r (code=exited, status=1/FAILURE)
 Main PID: 423 (code=exited, status=1/FAILURE)

Aug 16 08:44:54 archlinux sh[423]: user 'mysql': directory '/home/mysql' does not exist
Aug 16 08:44:54 archlinux sh[423]: user 'gdm': directory '/var/lib/gdm' does not exist
Aug 16 08:44:54 archlinux sh[423]: pwck: no changes
Aug 16 08:44:55 archlinux sh[423]: 'sefacs' is a member of the 'video' group in /etc/group but not in /etc/gshadow
Aug 16 08:44:55 archlinux sh[423]: 'sefacs' is a member of the 'vboxusers' group in /etc/group but not in /etc/gshadow
Aug 16 08:44:55 archlinux sh[423]: 'sefacs' is a member of the 'mysql' group in /etc/group but not in /etc/gshadow
Aug 16 08:44:55 archlinux sh[423]: 'sefacs' is a member of the 'clamav' group in /etc/group but not in /etc/gshadow
Aug 16 08:44:55 archlinux sh[423]: 'sddm' is a member of the 'video' group in /etc/gshadow but not in /etc/group
Aug 16 08:44:58 archlinux systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Aug 16 08:44:58 archlinux systemd[1]: shadow.service: Failed with result 'exit-code'.

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: inactive (dead)
Condition: start condition failed at Fri 2019-08-16 08:44:50 EEST; 6min ago
           `- ConditionNeedsUpdate=/etc was not met
     Docs: man:sysusers.d(5)
           man:systemd-sysusers.service(8)

Aug 16 08:44:50 archlinux systemd[1]: Condition check resulted in Create System Users being skipped.

loqs

Member

Registered: 2014-03-06

Posts: 19,101

Re: [Solved] Systemd-Sysusers.service suddenly failed

If grpck is not resolving the issues detected in post #1 have you tried resolving them with usermod?
Do you know how the inconsistencies could have been created such as by manually editing /etc/group or merging .pacnew files?

sefacs89

Member

Registered: 2019-08-12

Posts: 27

Re: [Solved] Systemd-Sysusers.service suddenly failed

If grpck is not resolving the issues detected in post #1 have you tried resolving them with usermod?
Do you know how the inconsistencies could have been created such as by manually editing /etc/group or merging .pacnew files?

i am sorry not ironic
but how usermod can help me restore the users and groups

the only thing that i have manually edited is virtualbox by adding sefacs at the end

but this problem didnt occur when i do it

its occured after a long period of time in the machine

can you or someone else help me with the usermod command

thanks

loqs

Member

Registered: 2014-03-06

Posts: 19,101

Re: [Solved] Systemd-Sysusers.service suddenly failed

The -G option to modify the supplementary groups,  the following drops sefacs from all supplementary groups apart from wheel then restores all the supplementary groups.

usermod -G  wheel sefacs
usermod -G  power,wheel,storage,video,vboxusers,mysql,clamav sefacs

See man 8 usermod.

sefacs89

Member

Registered: 2019-08-12

Posts: 27

Re: [Solved] Systemd-Sysusers.service suddenly failed

The -G option to modify the supplementary groups,  the following drops sefacs from all supplementary groups apart from wheel then restores all the supplementary groups.

usermod -G  wheel sefacs
usermod -G  power,wheel,storage,video,vboxusers,mysql,clamav sefacs

See man 8 usermod.

ok its weird enough
after restart

sudo systemctl --failed

the respond is : 0 loaded units listed

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: inactive (dead)
Condition: start condition failed at Fri 2019-08-16 16:39:40 EEST; 4min 13s ago
           `- ConditionNeedsUpdate=/etc was not met
     Docs: man:sysusers.d(5)
           man:systemd-sysusers.service(8)

Aug 16 16:39:40 archlinux systemd[1]: Condition check resulted in Create System Users being skipped.

sudo systemctl status shadow.service

* shadow.service - Verify integrity of password and group files
   Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2019-08-16 16:45:21 EEST; 5s ago
  Process: 1446 ExecStart=/bin/sh -c /usr/bin/pwck -r || r=1; /usr/bin/grpck -r && exit $r (code=exited, status=1/FAILURE)
 Main PID: 1446 (code=exited, status=1/FAILURE)

Aug 16 16:45:21 archlinux systemd[1]: Started Verify integrity of password and group files.
Aug 16 16:45:21 archlinux sh[1446]: user 'mysql': directory '/home/mysql' does not exist
Aug 16 16:45:21 archlinux sh[1446]: user 'gdm': directory '/var/lib/gdm' does not exist
Aug 16 16:45:21 archlinux sh[1446]: pwck: no changes
Aug 16 16:45:21 archlinux sh[1446]: 'sddm' is a member of the 'video' group in /etc/gshadow but not in /etc/group
Aug 16 16:45:21 archlinux systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Aug 16 16:45:21 archlinux systemd[1]: shadow.service: Failed with result 'exit-code'.

loqs

Member

Registered: 2014-03-06

Posts: 19,101

Re: [Solved] Systemd-Sysusers.service suddenly failed

What is weird?

ConditionNeedsUpdate=/etc was not met

The service does not need to run when there has been no change to /etc since it was last executed.
The other errors still exist as they have no been addressed.
sddm add or drop from the supplementary group video to sync group and gshadow.
You could check if the mysql user / group owns owns any files with find,  change the ownership to another user if they do then remove the user and group.  Same process for gdm.

sefacs89

Member

Registered: 2019-08-12

Posts: 27

Re: [Solved] Systemd-Sysusers.service suddenly failed

What is weird?

ConditionNeedsUpdate=/etc was not met

The service does not need to run when there has been no change to /etc since it was last executed.
The other errors still exist as they have no been addressed.
sddm add or drop from the supplementary group video to sync group and gshadow.
You could check if the mysql user / group owns owns any files with find,  change the ownership to another user if they do then remove the user and group.  Same process for gdm.

so i am ok
we fix the problem @ all?

thank you very much
for your help and your time

loqs

Member

Registered: 2014-03-06

Posts: 19,101

Re: [Solved] Systemd-Sysusers.service suddenly failed

The following will find any file object owned by user username or group username

# find / -user username -o -group groupname

The rest is using usermod which I have covered and userdel see their man pages plus Users_and_groups.
Edit:
Instead of removing the user and group you could change the users home directory to one that exists e.g. / with usermod.

Last edited by loqs (2019-08-16 15:24:38)

sefacs89

Member

Registered: 2019-08-12

Posts: 27

Re: [Solved] Systemd-Sysusers.service suddenly failed

The following will find any file object owned by user username or group username

# find / -user username -o -group groupname

The rest is using usermod which I have covered and userdel see their man pages plus Users_and_groups.
Edit:
Instead of removing the user and group you could change the users home directory to one that exists e.g. / with usermod.

thank you very much
for your time and help
i will mark it as solved