[SOLVED] shadow does not start due to user spamassassin

ploffie23 · 2022-01-05 13:20:40

The shadow service does not start.
I tried to create directory /var/lib/spamassassin, but that made no difference.

Output of systemctl status shadow.service

x shadow.service - Verify integrity of password and group files
     Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
     Active: failed (Result: exit-code) since Wed 2022-01-05 08:47:21 CET; 5h 6min ago
TriggeredBy: * shadow.timer
   Main PID: 14746 (code=exited, status=1/FAILURE)
        CPU: 57ms

Jan 05 08:47:21 LINUXPC systemd[1]: Started Verify integrity of password and group files.
Jan 05 08:47:21 LINUXPC sh[14755]: user 'spamd': directory '/var/lib/spamassassin' does not exist
Jan 05 08:47:21 LINUXPC sh[14755]: pwck: no changes
Jan 05 08:47:21 LINUXPC systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jan 05 08:47:21 LINUXPC systemd[1]: shadow.service: Failed with result 'exit-code'.

Output of journalctl -xe

Jan 05 13:58:31 LINUXPC kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=33:33:00:00:00:01:2c:3a:fd:ec:7d:48:86:dd SRC=fe80:0000:0000:0000:2e3a:>
Jan 05 13:59:16 LINUXPC kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=14:da:e9:64:ce:26:2c:3a:fd:ec:7d:48:08:00 SRC=192.168.178.1 DST=192.168>
Jan 05 13:59:17 LINUXPC kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=14:da:e9:64:ce:26:2c:3a:fd:ec:7d:48:08:00 SRC=192.168.178.1 DST=192.168>
Jan 05 13:59:19 LINUXPC kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=14:da:e9:64:ce:26:2c:3a:fd:ec:7d:48:08:00 SRC=192.168.178.1 DST=192.168>
Jan 05 13:59:23 LINUXPC kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=14:da:e9:64:ce:26:2c:3a:fd:ec:7d:48:08:00 SRC=192.168.178.1 DST=192.168>
Jan 05 13:59:29 LINUXPC NetworkManager[451]: <info>  [1641387569.3888] device (wlp3s0): set-hw-addr: set MAC address to 1A:BA:3E:99:87>
Jan 05 13:59:29 LINUXPC NetworkManager[451]: <info>  [1641387569.4073] device (wlp3s0): supplicant interface state: disconnected -> in>
Jan 05 13:59:29 LINUXPC NetworkManager[451]: <info>  [1641387569.4073] device (p2p-dev-wlp3s0): supplicant management interface state:>
Jan 05 13:59:29 LINUXPC NetworkManager[451]: <info>  [1641387569.4322] device (wlp3s0): supplicant interface state: interface_disabled>
Jan 05 13:59:29 LINUXPC NetworkManager[451]: <info>  [1641387569.4323] device (p2p-dev-wlp3s0): supplicant management interface state:>
Jan 05 13:59:49 LINUXPC kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:01:2c:3a:fd:ec:7d:48:08:00 SRC=192.168.178.1 DST=224.0.0>
Jan 05 14:01:01 LINUXPC CROND[22170]: (root) CMD (run-parts /etc/cron.hourly)
Jan 05 14:01:01 LINUXPC CROND[22169]: (root) CMDEND (run-parts /etc/cron.hourly)
Jan 05 14:01:54 LINUXPC kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:01:2c:3a:fd:ec:7d:48:08:00 SRC=192.168.178.1 DST=224.0.0>
Jan 05 14:03:30 LINUXPC mate-screensaver-dialog[22223]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/securit>
Jan 05 14:03:30 LINUXPC mate-screensaver-dialog[22223]: PAM adding faulty module: /usr/lib/security/pam_gnome_keyring.so
Jan 05 14:03:30 LINUXPC dbus-daemon[449]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedes>
Jan 05 14:03:30 LINUXPC dbus-daemon[449]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit d>
Jan 05 14:03:30 LINUXPC mate-screensaver-dialog[22223]: pam_systemd_home(mate-screensaver:auth): systemd-homed is not available: Unit >
Jan 05 14:03:34 LINUXPC audit[22270]: USER_AUTH pid=22270 uid=1000 auid=1000 ses=1 msg='op=PAM:unix_chkpwd acct="paul" exe="/usr/bin/u>
Jan 05 14:03:34 LINUXPC kernel: audit: type=1100 audit(1641387814.132:868): pid=22270 uid=1000 auid=1000 ses=1 msg='op=PAM:unix_chkpwd>
Jan 05 14:03:59 LINUXPC kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:01:2c:3a:fd:ec:7d:48:08:00 SRC=192.168.178.1 DST=224.0.0>
Jan 05 14:04:24 LINUXPC wnck-applet[729]: XID collision, trouble ahead

In /etc/group there is a line:

spamd:x:182:

In /etc/passwd there is a line:

spamd:x:182:182::/var/lib/spamassassin:/usr/bin/nologin

In /etc/shadow there is a line:

spamd:!*:18981::::::

spamassassin is not used, as far as I know.

[EDIT] removed spamd from /etc/group, /etc/passwd and /etc/gshadow/. Then started shadow and did "systemctl status shadow.services".
Is OK now and shadow.services is loaded, but
after "systemctl" there is still the complaint, that spamassassin.service is not found.

Can I mark this issue as SOLVED or should I do some more repairs??

[EDIT2] rebooted and "systemctl status" now shows "running" i.s.o. "degraded".

Last edited by ploffie23 (2022-01-05 18:18:53)

Arch Linux

#1 2022-01-05 13:20:40

[SOLVED] shadow does not start due to user spamassassin

Board footer