Hello,
Since the last system upgrade 2 days ago, some of the systemd services are failing at boot
I tried to search online for a similar case but no luck and I am unsure of the issue from looking at the logs
my apologies in advance if already reported and I missed it
Kernel: 7.0.13-arch1-1
Xfce 4.20
sudo systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● rc-local.service loaded failed failed Enable /etc/rc.local
● rsyslog.service loaded failed failed System Logging Service
● samba.service loaded failed failed Samba AD Daemon
● thermald.service loaded failed failed Thermal Daemon Service
● syslog.socket loaded failed failed Syslog Socket
Legend: 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.
5 loaded units listed.sudo systemctl status rsyslog.service
[sudo] password for sanzanmi:
Sorry, try again.
[sudo] password for sanzanmi:
× rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; preset: disabled)
Active: failed (Result: start-limit-hit) since Fri 2026-06-26 21:40:11 EDT; 27min ago
Invocation: 2ea5f93a9809439aa2d81578bb853730
TriggeredBy: × syslog.socket
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Process: 974 ExecStart=/usr/bin/rsyslogd -n -i /run/rsyslogd.pid (code=dumped, signal=SEGV)
Main PID: 974 (code=dumped, signal=SEGV)
Mem peak: 2M
CPU: 6ms
Jun 26 21:40:10 mainuser systemd[1]: Starting System Logging Service...
Jun 26 21:40:11 mainuser systemd-coredump[978]: [?] Process 974 (rsyslogd) of user 0 dumped core.
Stack trace of thread 974:
#0 0x00007f6c271e6e3b modff32x (libm.so.6 + 0x4ae3b)
#1 0x00007f6c27334a01 n/a (ld-linux-x86-64.so.2 + 0x10a01)
#2 0x00007f6c27335fb1 n/a (ld-linux-x86-64.so.2 + 0x11fb1)
#3 0x00007f6c2734641a n/a (ld-linux-x86-64.so.2 + 0x2241a)
#4 0x00007f6c27342d96 n/a (ld-linux-x86-64.so.2 + 0x1ed96)
#5 0x00007f6c273444c1 n/a (ld-linux-x86-64.so.2 + 0x204c1)
#6 0x00007f6c27343308 n/a (ld-linux-x86-64.so.2 + 0x1f308)
ELF object binary architecture: AMD x86-64
Jun 26 21:40:11 mainuser systemd[1]: rsyslog.service: Main process exited, code=dumped, status=11/SEGV
Jun 26 21:40:11 mainuser systemd[1]: rsyslog.service: Failed with result 'core-dump'.
lines 1-26 sudo systemctl status samba.service
× samba.service - Samba AD Daemon
Loaded: loaded (/usr/lib/systemd/system/samba.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Fri 2026-06-26 21:40:19 EDT; 29min ago
Invocation: 216a6ab7de05442aa948d8d76a922793
Docs: man:samba(8)
man:samba(7)
man:smb.conf(5)
Process: 1197 ExecStart=/usr/bin/samba --foreground --no-process-group $SAMBAOPTIONS (code=exited, status=1/>
Main PID: 1197 (code=exited, status=1/FAILURE)
Status: "daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for deta>
Error: code: 22 (Invalid argument)
Mem peak: 19.9M
CPU: 85ms
Jun 26 21:40:19 mainuser systemd[1]: Starting Samba AD Daemon...
Jun 26 21:40:19 mainuser samba[1197]: [2026/06/26 21:40:19.882139, 0] ../../source4/samba/server.c:862(binary>
Jun 26 21:40:19 mainuser samba[1197]: At this time the 'samba' binary should only be used for either:
Jun 26 21:40:19 mainuser samba[1197]: 'server role = active directory domain controller' or the rpc proxy wi>
Jun 26 21:40:19 mainuser samba[1197]: You should start smbd/nmbd/winbindd instead for domain member and stan>
Jun 26 21:40:19 mainuser samba[1197]: [2026/06/26 21:40:19.882213, 0] ../../lib/util/become_daemon.c:119(exit>
Jun 26 21:40:19 mainuser samba[1197]: exit_daemon: daemon failed to start: Samba detected misconfigured 'ser>
Jun 26 21:40:19 mainuser systemd[1]: samba.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 21:40:19 mainuser systemd[1]: samba.service: Failed with result 'exit-code'.
Jun 26 21:40:19 mainuser systemd[1]: Failed to start Samba AD Daemon.
ce; enabled; preset: disabled)
6-26 21:40:19 EDT; 29min ago
--no-process-group $SAMBAOPTIONS (code=exited, status=1/FAILURE)
configured 'server role' and exited. Check logs for details"
Daemon...
0:19.882139, 0] ../../source4/samba/server.c:862(binary_smbd_main)
he 'samba' binary should only be used for either:
active directory domain controller' or the rpc proxy with 'dcerpc endpoint servers = remote'
rt smbd/nmbd/winbindd instead for domain member and standalone file server tasks
0:19.882213, 0] ../../lib/util/become_daemon.c:119(exit_daemon)
aemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details, error code>
in process exited, code=exited, status=1/FAILURE
iled with result 'exit-code'.
amba AD Daemon.
~
~
× samba.service - Samba AD Daemon
Loaded: loaded (/usr/lib/systemd/system/samba.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Fri 2026-06-26 21:40:19 EDT; 29min ago
Invocation: 216a6ab7de05442aa948d8d76a922793
Docs: man:samba(8)
man:samba(7)
man:smb.conf(5)
Process: 1197 ExecStart=/usr/bin/samba --foreground --no-process-group $SAMBAOPTIONS (code=exited, status=1/>
Main PID: 1197 (code=exited, status=1/FAILURE)
Status: "daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for deta>
Error: code: 22 (Invalid argument)
Mem peak: 19.9M
CPU: 85ms
Jun 26 21:40:19 mainuser systemd[1]: Starting Samba AD Daemon...
Jun 26 21:40:19 mainuser samba[1197]: [2026/06/26 21:40:19.882139, 0] ../../source4/samba/server.c:862(binary>
Jun 26 21:40:19 mainuser samba[1197]: At this time the 'samba' binary should only be used for either:
Jun 26 21:40:19 mainuser samba[1197]: 'server role = active directory domain controller' or the rpc proxy wi>
Jun 26 21:40:19 mainuser samba[1197]: You should start smbd/nmbd/winbindd instead for domain member and stan>
Jun 26 21:40:19 mainuser samba[1197]: [2026/06/26 21:40:19.882213, 0] ../../lib/util/become_daemon.c:119(exit>
Jun 26 21:40:19 mainuser samba[1197]: exit_daemon: daemon failed to start: Samba detected misconfigured 'ser>
Jun 26 21:40:19 mainuser systemd[1]: samba.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 21:40:19 mainuser systemd[1]: samba.service: Failed with result 'exit-code'.
Jun 26 21:40:19 mainuser systemd[1]: Failed to start Samba AD Daemon.
~
~
ce; enabled; preset: disabled)
6-26 21:40:19 EDT; 29min ago
--no-process-group $SAMBAOPTIONS (code=exited, status=1/FAILURE)
configured 'server role' and exited. Check logs for details"
Daemon...
0:19.882139, 0] ../../source4/samba/server.c:862(binary_smbd_main)
he 'samba' binary should only be used for either:
active directory domain controller' or the rpc proxy with 'dcerpc endpoint servers = remote'
rt smbd/nmbd/winbindd instead for domain member and standalone file server tasks
0:19.882213, 0] ../../lib/util/become_daemon.c:119(exit_daemon)
aemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details, error code>
in process exited, code=exited, status=1/FAILURE
iled with result 'exit-code'.
amba AD Daemon.
~
~
FAILURE)
ils"sudo journalctl --since today | grep -i rsyslog
Jun 16 23:31:26 mainuser rsyslogd[731]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="731" x-info="https://www.rsyslog.com"] exiting on signal 15.
Jun 16 23:31:26 mainuser systemd[1]: rsyslog.service: Deactivated successfully.
Jun 16 23:31:26 mainuser systemd[1]: rsyslog.service: Consumed 6min 24.233s CPU time over 1w 3d 2h 34min 25.418s wall clock time, 269.4M memory peak.
Jun 16 23:32:15 mainuser rsyslogd[733]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2604.0]
Jun 16 23:32:15 mainuser rsyslogd[733]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="733" x-info="https://www.rsyslog.com"] start
Jun 19 20:07:50 mainuser rsyslogd[733]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="733" x-info="https://www.rsyslog.com"] exiting on signal 15.
Jun 19 20:07:50 mainuser systemd[1]: rsyslog.service: Deactivated successfully.
Jun 19 20:07:50 mainuser systemd[1]: rsyslog.service: Consumed 3min 38.838s CPU time over 2d 20h 35min 34.489s wall clock time, 236.7M memory peak.
Jun 19 20:08:39 mainuser rsyslogd[736]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2604.0]
Jun 19 20:08:39 mainuser rsyslogd[736]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="736" x-info="https://www.rsyslog.com"] start
Jun 19 20:08:39 mainuser rsyslogd[736]: action 'action-17-builtin:ompipe' suspended (module 'builtin:ompipe'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2604.0 try https://www.rsyslog.com/e/2007 ]
Jun 19 20:08:39 mainuser rsyslogd[736]: action 'action-17-builtin:ompipe' suspended (module 'builtin:ompipe'), next retry is Fri Jun 19 20:09:09 2026, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.2604.0 try https://www.rsyslog.com/e/2007 ]
Jun 19 20:09:09 mainuser rsyslogd[736]: action 'action-17-builtin:ompipe' resumed (module 'builtin:ompipe') [v8.2604.0 try https://www.rsyslog.com/e/2359 ]
Jun 21 00:58:18 mainuser rsyslogd[736]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="736" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Jun 22 06:20:35 mainuser rsyslogd[736]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="736" x-info="https://www.rsyslog.com"] exiting on signal 15.
Jun 22 06:20:35 mainuser systemd[1]: rsyslog.service: Deactivated successfully.
Jun 22 06:20:35 mainuser systemd[1]: rsyslog.service: Consumed 1min 20.545s CPU time over 2d 10h 11min 55.188s wall clock time, 81.6M memory peak.
Jun 22 06:21:23 mainuser rsyslogd[739]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2604.0]
Jun 22 06:21:23 mainuser rsyslogd[739]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="739" x-info="https://www.rsyslog.com"] start
Jun 22 06:21:24 mainuser rsyslogd[739]: action 'action-17-builtin:ompipe' suspended (module 'builtin:ompipe'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2604.0 try https://www.rsyslog.com/e/2007 ]
Jun 22 06:21:24 mainuser rsyslogd[739]: action 'action-17-builtin:ompipe' suspended (module 'builtin:ompipe'), next retry is Mon Jun 22 06:21:54 2026, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.2604.0 try https://www.rsyslog.com/e/2007 ]
Jun 22 06:22:20 mainuser rsyslogd[739]: action 'action-17-builtin:ompipe' resumed (module 'builtin:ompipe') [v8.2604.0 try https://www.rsyslog.com/e/2359 ]
Jun 22 06:38:15 mainuser rsyslogd[739]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="739" x-info="https://www.rsyslog.com"] exiting on signal 15.
Jun 22 06:38:15 mainuser systemd[1]: rsyslog.service: Deactivated successfully.
Jun 22 06:38:46 mainuser rsyslogd[732]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2604.0]
Jun 22 06:38:46 mainuser rsyslogd[732]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="732" x-info="https://www.rsyslog.com"] start
Jun 22 06:38:47 mainuser rsyslogd[732]: action 'action-17-builtin:ompipe' suspended (module 'builtin:ompipe'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2604.0 try https://www.rsyslog.com/e/2007 ]
Jun 22 06:38:47 mainuser rsyslogd[732]: action 'action-17-builtin:ompipe' suspended (module 'builtin:ompipe'), next retry is Mon Jun 22 06:39:17 2026, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.2604.0 try https://www.rsyslog.com/e/2007 ]
Jun 22 06:39:17 mainuser rsyslogd[732]: action 'action-17-builtin:ompipe' resumed (module 'builtin:ompipe') [v8.2604.0 try https://www.rsyslog.com/e/2359 ]
Jun 24 23:49:32 mainuser rsyslogd[732]: [origin software="rsyslogd" swVersion="8.2604.0" x-pid="732" x-info="https://www.rsyslog.com"] exiting on signal 15.
Jun 24 23:49:32 mainuser systemd[1]: rsyslog.service: Deactivated successfully.
Jun 24 23:49:32 mainuser systemd[1]: rsyslog.service: Consumed 1min 25.266s CPU time over 2d 17h 10min 45.482s wall clock time, 64M memory peak.
Jun 24 23:50:22 mainuser systemd-coredump[754]: Process 744 (rsyslogd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Jun 24 23:50:23 mainuser systemd-coredump[796]: Process 744 (rsyslogd) of user 0 dumped core.
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Main process exited, code=dumped, status=11/SEGV
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Failed with result 'core-dump'.
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 1.
Jun 24 23:50:23 mainuser systemd-coredump[813]: Process 811 (rsyslogd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Jun 24 23:50:23 mainuser systemd-coredump[814]: Process 811 (rsyslogd) of user 0 dumped core.
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Main process exited, code=dumped, status=11/SEGV
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Failed with result 'core-dump'.
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 2.
Jun 24 23:50:23 mainuser systemd-coredump[838]: Process 834 (rsyslogd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Jun 24 23:50:23 mainuser systemd-coredump[840]: Process 834 (rsyslogd) of user 0 dumped core.
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Main process exited, code=dumped, status=11/SEGV
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Failed with result 'core-dump'.
Jun 24 23:50:23 mainuser systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 3.
Jun 24 23:50:24 mainuser systemd-coredump[981]: Process 979 (rsyslogd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Jun 24 23:50:24 mainuser systemd-coredump[984]: Process 979 (rsyslogd) of user 0 dumped core.
Jun 24 23:50:24 mainuser systemd[1]: rsyslog.service: Main process exited, code=dumped, status=11/SEGV
Jun 24 23:50:24 mainuser systemd[1]: rsyslog.service: Failed with result 'core-dump'.
Jun 24 23:50:24 mainuser systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 4.
Jun 24 23:50:24 mainuser systemd-coredump[1022]: Process 1021 (rsyslogd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Jun 24 23:50:24 mainuser systemd-coredump[1023]: Process 1021 (rsyslogd) of user 0 dumped core.
Jun 24 23:50:24 mainuser systemd[1]: rsyslog.service: Main process exited, code=dumped, status=11/SEGV
Jun 24 23:50:24 mainuser systemd[1]: rsyslog.service: Failed with result 'core-dump'.此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。