Created attachment 875329 [details]
yast logs

install and enable cockpit.socket on my RPi 4.

Go to and check cockpit WebUI. I found that an error shows up under Services: setroubleshootd failed to start.

I tried to restart it without success.


--

localhost:/tmp # systemctl status setroubleshootd.service
× setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
     Active: failed (Result: exit-code) since Wed 2024-06-05 12:08:57 UTC; 1min 14s ago
    Process: 8552 ExecStart=/usr/sbin/setroubleshootd -f (code=exited, status=3)
   Main PID: 8552 (code=exited, status=3)
        CPU: 1.832s

Jun 05 12:08:55 localhost.localdomain systemd[1]: Starting SETroubleshoot daemon for processing new SELinux denial logs...
Jun 05 12:08:56 localhost.localdomain setroubleshoot[8552]: SELinux not enabled, setroubleshootd exiting...
Jun 05 12:08:57 localhost.localdomain systemd[1]: setroubleshootd.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Jun 05 12:08:57 localhost.localdomain systemd[1]: setroubleshootd.service: Failed with result 'exit-code'.
Jun 05 12:08:57 localhost.localdomain systemd[1]: Failed to start SETroubleshoot daemon for processing new SELinux denial logs.
Jun 05 12:08:57 localhost.localdomain systemd[1]: setroubleshootd.service: Consumed 1.832s CPU time.
localhost:/tmp # systemctl restart setroubleshootd.service
Job for setroubleshootd.service failed because the control process exited with error code.
See "systemctl status setroubleshootd.service" and "journalctl -xeu setroubleshootd.service" for details.
localhost:/tmp # journalctl -xeu setroubleshootd
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit setroubleshootd.service completed and consumed the indicated resources.
Jun 05 12:10:25 localhost.localdomain systemd[1]: Starting SETroubleshoot daemon for processing new SELinux denial logs...
░░ Subject: A start job for unit setroubleshootd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit setroubleshootd.service has begun execution.
░░ 
░░ The job identifier is 8434.
Jun 05 12:10:27 localhost.localdomain setroubleshoot[8592]: SELinux not enabled, setroubleshootd exiting...
Jun 05 12:10:27 localhost.localdomain systemd[1]: setroubleshootd.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit setroubleshootd.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 3.
Jun 05 12:10:27 localhost.localdomain systemd[1]: setroubleshootd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit setroubleshootd.service has entered the 'failed' state with result 'exit-code'.
Jun 05 12:10:27 localhost.localdomain systemd[1]: Failed to start SETroubleshoot daemon for processing new SELinux denial logs.
░░ Subject: A start job for unit setroubleshootd.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit setroubleshootd.service has finished with a failure.
░░ 
░░ The job identifier is 8434 and the job result is failed.
Jun 05 12:10:27 localhost.localdomain systemd[1]: setroubleshootd.service: Consumed 2.058s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit setroubleshootd.service completed and consumed the indicated resources.