You are not logged in.
- Topics: Active | Unanswered
#1 2020-05-24 10:11:02
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,473
Systemd services with dropped "CAPS" started to segfault.
Hi,
I'm facing a strange issue with a remote workstation running arch.
basically every systemd service that contains: ProtectKernelModules=yes produces a segfault.
even the most basic one:
[Unit]
Description=testservice
[Service]
Type=oneshot
ExecStart=/usr/bin/sleep 1
ProtectKernelModules=truekoko@Gozer# systemctl daemon-reload ; systemctl start tryme
Job for tryme.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status tryme.service" and "journalctl -xe" for details.
# journalctl -xe
-- The job identifier is 1673548.
May 24 11:51:01 Gozer kernel: (sleep)[2230636]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680>
May 24 11:51:01 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 f>
May 24 11:51:01 Gozer systemd[1]: tryme.service: Main process exited, code=dumped, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- An ExecStart= process belonging to unit tryme.service has exited.
--
-- The process' exit code is 'dumped' and its exit status is 11.
May 24 11:51:01 Gozer systemd[1]: tryme.service: Failed with result 'core-dump'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit tryme.service has entered the 'failed' state with result 'core-dump'.
May 24 11:51:01 Gozer systemd[1]: Failed to start testservice.
-- Subject: A start job for unit tryme.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit tryme.service has finished with a failure.I discovered the issue because logrotate and fstrim services were crashing everytime the systemd timer were triggered, but the crashes beginning to happen on may 8, and the client uptime is 81 days.
In the meantime i did no package upgrades to the system, so i must have been done something weird that broke it.
Anyway, since i've no physical access to the workstation and i will not have it until september, id' prefer to NOT reboot the machine remotely; at least not in this state.
In this workstation i've coredump facility turned off, anyway:
koko@Gozer# coredumpctl
TIME PID UID GID SIG COREFILE EXE
Tue 2020-05-05 15:07:50 CEST 3619793 1012 1012 11 none /usr/bin/kded5
Tue 2020-05-05 15:22:49 CEST 793053 1012 1012 11 none /usr/bin/kded5
Tue 2020-05-05 15:41:20 CEST 804570 1012 1012 11 none /usr/bin/kded5
Tue 2020-05-05 15:42:15 CEST 817113 1012 1012 11 none /usr/bin/kded5
Fri 2020-05-08 12:41:38 CEST 3324100 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324106 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324104 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324120 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324113 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324116 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324117 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324096 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324118 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324102 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324114 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324099 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324112 1012 1012 11 none /usr/bin/python3.8...while if i search in the journal:
koko@Gozer# journalctl |grep segfault|head -n 100
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324120]: segfault at 18 ip 00007f4de1625dfc sp 00007ffdf2350e50 error 4
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324117]: segfault at 18 ip 00007fc154a0cdfc sp 00007ffff2b92750 error 4
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324118]: segfault at 18 ip 00007fb69afcedfc sp 00007ffe53b63f20 error 4
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324102]: segfault at 18 ip 00007fd9939f1dfc sp 00007ffe633c6330 error 4 in libgtk-3.so.0.2407.7[7fd99371f000+356000]
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324100]: segfault at 18 ip 00007f86241d6dfc sp 00007fffbd55c7e0 error 4 in libgtk-3.so.0.2407.7[7f8623f04000+356000]
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324106]: segfault at 18 ip 00007f8f89645dfc sp 00007fff51b94190 error 4 in libgtk-3.so.0.2407.7[7f8f89373000+356000]
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324096]: segfault at 18 ip 00007f871bed2dfc sp 00007ffe2a340000 error 4 in libgtk-3.so.0.2407.7[7f871bc00000+356000]
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324099]: segfault at 18 ip 00007fbf2160ddfc sp 00007ffe3b912aa0 error 4 in libgtk-3.so.0.2407.7[7fbf2133b000+356000]
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324112]: segfault at 18 ip 00007eff94fe9dfc sp 00007ffdae317670 error 4 in libgtk-3.so.0.2407.7[7eff94d17000+356000]
May 08 12:41:37 Gozer kernel: scp-dbus-servic[3324113]: segfault at 18 ip 00007f026bfa4dfc sp 00007ffe38f8f610 error 4 in libgtk-3.so.0.2407.7[7f026bcd2000+356000]
May 08 12:47:40 Gozer kernel: (ostnamed)[3328972]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328976]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328981]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328984]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328986]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328989]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328991]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328993]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328995]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 12:47:40 Gozer kernel: (coredump)[3328999]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (ostnamed)[3437095]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437104]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437108]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437111]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437121]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437128]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437132]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437144]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437147]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:27:41 Gozer kernel: (coredump)[3437149]: segfault at 7f493fe3c9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (ostnamed)[3444807]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444812]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444815]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444817]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444819]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444822]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444825]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444828]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444838]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 08 15:32:46 Gozer kernel: (coredump)[3444841]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (ogrotate)[3764818]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764825]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764828]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764831]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764833]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764835]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764837]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764839]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764846]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 00:00:00 Gozer kernel: (coredump)[3764848]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: scan-thread[3313018]: segfault at 746165 ip 00007f3bfc512c9b sp 00007f3be7ffeb60 error 4 in libc-2.31.so[7f3bfc4c3000+14c000]
May 09 10:07:05 Gozer kernel: (coredump)[4129354]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: (coredump)[4129356]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: (coredump)[4129358]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: (coredump)[4129361]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: (coredump)[4129363]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: (coredump)[4129365]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: (coredump)[4129367]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: (coredump)[4129369]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:07:05 Gozer kernel: (coredump)[4129371]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:41 Gozer kernel: (coredump)[4149527]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149529]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149533]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149535]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149538]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149545]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149549]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149555]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149564]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:09:42 Gozer kernel: (coredump)[4149566]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:29 Gozer kernel: (coredump)[4160658]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:29 Gozer kernel: (coredump)[4160660]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:29 Gozer kernel: (coredump)[4160663]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:29 Gozer kernel: (coredump)[4160671]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:29 Gozer kernel: (coredump)[4160675]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:29 Gozer kernel: (coredump)[4160677]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:30 Gozer kernel: (coredump)[4160679]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:30 Gozer kernel: (coredump)[4160685]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:30 Gozer kernel: (coredump)[4160687]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:24:30 Gozer kernel: (coredump)[4160689]: segfault at 7f494063d9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4161979]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4161981]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4161984]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4161991]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4161996]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4161998]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4162000]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4162002]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4162004]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 09 10:25:47 Gozer kernel: (coredump)[4162006]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (ogrotate)[523343]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523348]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523350]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523353]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523357]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523359]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523361]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523363]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523370]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
May 10 00:00:00 Gozer kernel: (coredump)[523372]: segfault at 7f493de389d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]they are all crashing at the same address, same instruction pointer, same stack pointer...
I enabled the creation of cores and explored one:
GNU gdb (GDB) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/sleep...
(No debugging symbols found in /usr/bin/sleep)
warning: core file may not match specified executable file.
[New LWP 2230636]
Core was generated by `(sleep)'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f4941fec4cb in ?? ()
(gdb) thread apply all bt
Thread 1 (LWP 2230636):
#0 0x00007f4941fec4cb in ?? ()
#1 0x00007f4941641140 in ?? ()
#2 0x00007f4942339400 in ?? ()
#3 0x0000000000000000 in ?? ()
(gdb) Not much useful information...
Any idea/suggestion?
Thanks.
Last edited by kokoko3k (2020-05-25 07:43:51)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
#2 2020-05-24 12:54:27
- Ropid
- Member
- Registered: 2015-03-09
- Posts: 1,069
Re: Systemd services with dropped "CAPS" started to segfault.
Here's the documentation for the ProtectKernelModules setting, maybe something mentioned there helps with your search:
ProtectKernelModules=
Takes a boolean argument. If true, explicit module loading will be denied. This allows module load and unload operations to be turned off on modular kernels. It is recommended to turn this on for most services that do not need special file systems or extra kernel modules to work. Defaults to off. Enabling this option removes CAP_SYS_MODULE from the capability bounding set for the unit, and installs a system call filter to block module system calls, also /usr/lib/modules is made inaccessible. For this setting the same restrictions regarding mount propagation and privileges apply as for ReadOnlyPaths= and related calls, see above. Note that limited automatic module loading due to user configuration or kernel mapping tables might still happen as side effect of requested user operations, both privileged and unprivileged. To disable module auto-load feature please see sysctl.d(5) kernel.modules_disabled mechanism and /proc/sys/kernel/modules_disabled documentation. If turned on and if running in user mode, or in system mode, but without the CAP_SYS_ADMIN capability (e.g. setting User=), NoNewPrivileges=yes is implied.
This option is only available for system services and is not supported for services running in per-user instances of the service manager.
I found this in "man systemd.exec".
Offline
#3 2020-05-24 14:39:23
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,473
Re: Systemd services with dropped "CAPS" started to segfault.
Thanks Ropid, i tried to replicate the crash by dropping cap_sys_module that way:
root@Gozer# capsh --print
Current: =ep
Bounding set =cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_module,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_mac_override,cap_mac_admin,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read
Ambient set =
Securebits: 00/0x0/1'b0
secure-noroot: no (unlocked)
secure-no-suid-fixup: no (unlocked)
secure-keep-caps: no (unlocked)
secure-no-ambient-raise: no (unlocked)
uid=0(root) euid=0(root)
gid=0(root)
groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),19(log),92(audio),1000(socketsentry)
Guessed mode: UNCERTAIN (0)
[16:37:03] cd ~
root@Gozer# capsh --drop=cap_sys_module --
-------------------------------
..:: mEsSaGe oF tHe dAy ;) ::..
-------------------------------
<cas> well there ya go. say something stupid in irc and have it
immortalised forever in someone's .sig file
[16:37:18] cd ~
root@Gozer# capsh --print
Current: =ep cap_sys_module-ep
Bounding set =cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_mac_override,cap_mac_admin,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read
Ambient set =
Securebits: 00/0x0/1'b0
secure-noroot: no (unlocked)
secure-no-suid-fixup: no (unlocked)
secure-keep-caps: no (unlocked)
secure-no-ambient-raise: no (unlocked)
uid=0(root) euid=0(root)
gid=0(root)
groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),19(log),92(audio),1000(socketsentry)
Guessed mode: UNCERTAIN (0)
[16:37:21] cd ~
root@Gozer# sleep 2I'm not entirely sure, but it seems that the bash capsh spawned has no cap_sys_module and, "unfortunately" it didn't segfaulted as the systemd services do.
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
#4 2020-05-24 18:25:38
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,041
Re: Systemd services with dropped "CAPS" started to segfault.
If the client uptime is 81 days does it need a reboot for a new kernel version? Was there a pacman update on May 8? Please post some ungrepped journal contents showing a service start through to coredump.
Offline
#5 2020-05-25 07:21:49
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,473
Re: Systemd services with dropped "CAPS" started to segfault.
I noticed that there are other "hardening" directives that make the services crash, (bolded them), while other listed are fine.
LockPersonality=true
MemoryDenyWriteExecute=true
ProtectControlGroups=true
ProtectKernelTunables=true
ProtectSystem=full
RestrictNamespaces=true
RestrictRealtime=true
ProtectKernelLogs=true
PrivateDevices=true
As far as i can read from man systemd.exec they all seems to remove a CAP_*
so, i used the following systemd directive, alone:
CapabilityBoundingSet=CAP_CHOWN CAP_DAC_OVERRIDE CAP_DAC_READ_SEARCH CAP_FOWNER CAP_FSETID CAP_KILL CAP_SETGID CAP_SETUID CAP_SETPCAP CAP_LINUX_IMMUTABLE CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_ADMIN CAP_NET_RAW CAP_IPC_LOCK CAP_IPC_OWNER CAP_SYS_MODULE CAP_SYS_RAWIO CAP_SYS_CHROOT CAP_SYS_PTRACE CAP_SYS_PACCT CAP_SYS_ADMIN CAP_SYS_BOOT CAP_SYS_NICE CAP_SYS_RESOURCE CAP_SYS_TIME CAP_SYS_TTY_CONFIG CAP_MKNOD CAP_LEASE CAP_AUDIT_WRITE CAP_AUDIT_CONTROL CAP_SETFCAP CAP_MAC_OVERRIDE CAP_MAC_ADMIN CAP_SYSLOG CAP_WAKE_ALARM CAP_BLOCK_SUSPEND CAP_AUDIT_READ...which basically set ALL of the supported capabilities to the service and it does NOT crash.
Stripping from the list CAP_SYSMODULE or CAP_MKNOD or CAP_RAWIO(like PrivateDevices and ProtectKernelLogs do) makes it crash; I tried to strip other capabilities too (one at a time), and it crashes.
I'll edit the topic...
loqs wrote:
If the client uptime is 81 days does it need a reboot for a new kernel version? Was there a pacman update on May 8? Please post some ungrepped journal contents showing a service start through to coredump.
Kernel is fine:
koko@Gozer# uname -a
Linux Gozer 5.5.7-arch1-1 #1 SMP PREEMPT Sat, 29 Feb 2020 19:06:02 +0000 x86_64 GNU/Linux
koko@Gozer# pacman -Q linux
linux 5.5.7.arch1-1Here are what happened in may on packages:
koko@Gozer# grep "2020-05" /var/log/pacman.log|grep 'upgraded\|installed'
[2020-05-07T14:00:50+0200] [ALPM] installed mosh (1.3.2-11)
[2020-05-07T14:32:45+0200] [ALPM] reinstalled shellinabox-git (r431.4f0ecc3-1)
[2020-05-19T07:54:31+0200] [ALPM] installed python-shiboken2 (5.14.1-1)
[2020-05-19T07:54:31+0200] [ALPM] installed patchelf (0.9-2)
[2020-05-19T07:54:41+0200] [ALPM] installed anydesk-bin (5.5.6-3)
[2020-05-22T08:48:22+0200] [ALPM] upgraded qbittorrent (4.2.1-1 -> 4.2.5-1)
[2020-05-22T14:17:55+0200] [ALPM] upgraded libtorrent-rasterbar (1:1.2.4-1 -> 1:1.2.6-1)
[2020-05-22T14:20:31+0200] [ALPM] upgraded higgins-git (20160527-1 -> 20200522-1)
[2020-05-24T11:20:23+0200] [ALPM] reinstalled iputils (20190709-2)
[2020-05-24T11:41:48+0200] [ALPM] upgraded logrotate (3.15.1-2 -> 3.16.0-1)(last logrotate upgrade was via makepkg to test if the issue was with logrotate itself.)
koko@Gozer# cat /etc/systemd/system/tryme.service
[Unit]
Description=testservice
[Service]
Type=oneshot
#ExecStart=/usr/sbin/logrotate /etc/logrotate.conf
ExecStart=/usr/bin/sleep 10
ProtectKernelModules=true
koko@Gozer# systemctl start tryme
Job for tryme.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status tryme.service" and "journalctl -xe" for details.mag 25 08:35:17 Gozer systemd[1]: Starting testservice...
mag 25 08:35:17 Gozer kernel: show_signal_msg: 7 callbacks suppressed
mag 25 08:35:17 Gozer kernel: (sleep)[3084845]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084846/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084847]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084848/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084849]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084850/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084851]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084852/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084853]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084854/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084855]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084856/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084857]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084858/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084859]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084860/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084861]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084862/UID 0).
mag 25 08:35:17 Gozer kernel: (coredump)[3084863]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]
mag 25 08:35:17 Gozer kernel: Code: 24 40 0f 29 6c 24 50 0f 29 74 24 60 0f 29 7c 24 70 e9 54 ff ff ff e8 04 62 ff ff 0f 1f 40 00 f3 0f 1e fa 41 54 55 48 83 ec 08 <8b> af d0 02 00 00 85 ed 7e 43 8d 56 e0 41 89 f4 b8 16 00 00 00 83
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084864/UID 0).
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084866/UID 0).
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084868/UID 0).
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084870/UID 0).
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084872/UID 0).
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084874/UID 0).
mag 25 08:35:17 Gozer systemd[1]: Started Process Core Dump (PID 3084876/UID 0).
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump.socket: Too many incoming connections (16), dropping connection.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1494-3084876-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1493-3084874-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1492-30
4872-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1491-3084870-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1490-3084868-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1489-3084866-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1488-3084864-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1487-3084862-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1486-3084860-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1485-3084858-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1484-3084856-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1483-3084854-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1482-3084852-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1481-3084850-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1480-3084848-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: systemd-coredump@1479-3084846-0.service: Succeeded.
mag 25 08:35:17 Gozer systemd[1]: tryme.service: Main process exited, code=dumped, status=11/SEGV
mag 25 08:35:17 Gozer systemd[1]: tryme.service: Failed with result 'core-dump'.
mag 25 08:35:17 Gozer systemd[1]: Failed to start testservice....systemd-coredump@.service itself is crashing for the same reason.
Indeed, it stopped working may, 8 too:
koko@Gozer# coredumpctl
TIME PID UID GID SIG COREFILE EXE
Tue 2020-05-05 15:07:50 CEST 3619793 1012 1012 11 none /usr/bin/kded5
Tue 2020-05-05 15:22:49 CEST 793053 1012 1012 11 none /usr/bin/kded5
Tue 2020-05-05 15:41:20 CEST 804570 1012 1012 11 none /usr/bin/kded5
Tue 2020-05-05 15:42:15 CEST 817113 1012 1012 11 none /usr/bin/kded5
Fri 2020-05-08 12:41:38 CEST 3324100 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324106 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324104 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324120 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324113 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324116 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324117 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324096 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324118 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324102 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324114 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324099 1012 1012 11 none /usr/bin/python3.8
Fri 2020-05-08 12:41:38 CEST 3324112 1012 1012 11 none /usr/bin/python3.8Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
#6 2020-05-25 07:39:53
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,473
Re: Systemd services with dropped "CAPS" started to segfault.
Oh, it seems i messed around with cgroups on may, 07; from the bash history:
49401 2020-05-07 18:10:08 cd /sys/fs/cgroup/
49402 2020-05-07 18:10:31 mkdir prova #<--- this failed
49403 2020-05-07 18:11:10 cgcreate -a koko -g net_cls:koko --v
49404 2020-05-07 18:11:41 cgcreate -a koko:koko -t koko:koko -g net_cls:retelimitata
49405 2020-05-07 18:11:43 ls
49406 2020-05-07 18:11:47 ls -la
49407 2020-05-07 18:11:55 mount
49408 2020-05-07 18:11:58 mount|grep -i cg
49409 2020-05-07 18:12:42 ls /sys/fs/cgroup/net_cls/retelimitata/
49410 2020-05-07 18:13:28 ls -la
49411 2020-05-07 18:13:34 cd net_cls/
49412 2020-05-07 18:13:34 ls
49413 2020-05-07 18:13:41 cat tasks
49414 2020-05-07 18:13:48 cd retelimitata/
49415 2020-05-07 18:13:50 ls -la
49416 2020-05-07 18:14:10 /bin/echo 2048 > net.tcp
49417 2020-05-07 18:14:12 sudo /bin/echo 2048 > net.tcp
49418 2020-05-07 18:14:17 LC_ALL=C sudo /bin/echo 2048 > net.tcp
49419 2020-05-07 18:14:24 LC_ALL=C /bin/echo 2048 > net.tcp
49420 2020-05-07 18:14:32 export LC_ALL=C ; /bin/echo 2048 > net.tcpAnyway, i deleted it right now via cgdelete, but nothing is changed.
-edit-
crashing too:
systemd-run --property=PrivateDevices=true ls
[7080612.492127] (ls)[3137696]: segfault at 7f494163f9d0 ip 00007f4941fec4cb sp 00007ffd8823e680 error 4 in libpthread-2.31.so[7f4941fe2000+10000]I managed to attach strace to pid 1 and produced a log of the crash ** 4.9MB of text ** )
https://0x0.st/ipLH.log
There are a lot of errors, but i don't know what of them are relevant.
But what happens before every segfault is capset:
3143612 capset({version=_LINUX_CAPABILITY_VERSION_3, pid=0}, {effective=1<<CAP_CHOWN|1<<CAP_DAC_OVERRIDE|1<<CAP_DAC_READ_SEARCH|1<<CAP_FOWNER|1<<CAP_FSETID|1<<CAP_KILL|1<<CAP_SETGID|1<<CAP_SETUID|1<<CAP_SETPCAP|1<<CAP_LINUX_IMMUTABLE|1<<CAP_NET_BIND_SERVICE|1<<CAP_NET_BROADCAST|1<<CAP_NET_ADMIN|1<<CAP_NET_RAW|1<<CAP_IPC_LOCK|1<<CAP_IPC_OWNER|1<<CAP_SYS_MODULE|1<<CAP_SYS_RAWIO|1<<CAP_SYS_CHROOT|1<<CAP_SYS_PTRACE|1<<CAP_SYS_PACCT|1<<CAP_SYS_ADMIN|1<<CAP_SYS_BOOT|1<<CAP_SYS_NICE|1<<CAP_SYS_RESOURCE|1<<CAP_SYS_TIME|1<<CAP_SYS_TTY_CONFIG|1<<CAP_MKNOD|1<<CAP_LEASE|1<<CAP_AUDIT_WRITE|1<<CAP_AUDIT_CONTROL|1<<CAP_SETFCAP|1<<CAP_MAC_OVERRIDE|1<<CAP_MAC_ADMIN|1<<CAP_SYSLOG|1<<CAP_WAKE_ALARM|1<<CAP_BLOCK_SUSPEND|1<<CAP_AUDIT_READ, permitted=1<<CAP_CHOWN|1<<CAP_DAC_OVERRIDE|1<<CAP_DAC_READ_SEARCH|1<<CAP_FOWNER|1<<CAP_FSETID|1<<CAP_KILL|1<<CAP_SETGID|1<<CAP_SETUID|1<<CAP_SETPCAP|1<<CAP_LINUX_IMMUTABLE|1<<CAP_NET_BIND_SERVICE|1<<CAP_NET_BROADCAST|1<<CAP_NET_ADMIN|1<<CAP_NET_RAW|1<<CAP_IPC_LOCK|1<<CAP_IPC_OWNER|1<<CAP_SYS_MODULE|1<<CAP_SYS_RAWIO|1<<CAP_SYS_CHROOT|1<<CAP_SYS_PTRACE|1<<CAP_SYS_PACCT|1<<CAP_SYS_ADMIN|1<<CAP_SYS_BOOT|1<<CAP_SYS_NICE|1<<CAP_SYS_RESOURCE|1<<CAP_SYS_TIME|1<<CAP_SYS_TTY_CONFIG|1<<CAP_MKNOD|1<<CAP_LEASE|1<<CAP_AUDIT_WRITE|1<<CAP_AUDIT_CONTROL|1<<CAP_SETFCAP|1<<CAP_MAC_OVERRIDE|1<<CAP_MAC_ADMIN|1<<CAP_SYSLOG|1<<CAP_WAKE_ALARM|1<<CAP_BLOCK_SUSPEND|1<<CAP_AUDIT_READ, inheritable=0}) = 0
3143612 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7f494163f9d0} ---Last edited by kokoko3k (2020-05-26 13:45:40)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline