I started noticing a service failure when shutting down my machine and was wondering if anyone can tell me if it’s serious. journalctl -xe | grep fail gives me this:
░░ Subject: Unit failed
░░ The unit UNIT has entered the 'failed' state with result 'resources'.
░░ Subject: A start job for unit UNIT has failed
░░ The job identifier is 130 and the job result is failed.
░░ Subject: Unit failed
░░ The unit sssd-kcm.service has entered the 'failed' state with result 'exit-code'.
feb. 26 00:08:10 fedora-desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kcm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
░░ Subject: Unit failed
░░ The unit sssd-kcm.service has entered the 'failed' state with result 'exit-code'.
feb. 26 00:08:10 fedora-desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kcm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
░░ Subject: Unit failed
░░ The unit sssd-kcm.service has entered the 'failed' state with result 'exit-code'.
feb. 26 00:08:10 fedora-desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kcm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
░░ Subject: Unit failed
░░ The unit sssd-kcm.service has entered the 'failed' state with result 'exit-code'.
feb. 26 00:08:10 fedora-desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kcm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
░░ Subject: Unit failed
░░ The unit sssd-kcm.service has entered the 'failed' state with result 'exit-code'.
feb. 26 00:08:10 fedora-desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kcm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
░░ Subject: Unit failed
░░ The unit sssd-kcm.service has entered the 'failed' state with result 'exit-code'.
░░ Subject: A start job for unit sssd-kcm.service has failed
░░ The job identifier is 3574 and the job result is failed.
░░ Subject: Unit failed
░░ The unit sssd-kcm.socket has entered the 'failed' state with result 'service-start-limit-hit'.
feb. 26 00:08:11 fedora-desktop gsd-color[2050]: failed to set screen _ICC_PROFILE: Failed to open file “/home/zeno/.local/share/icc/edid-ed14a1c8ed95d56b18c24bb372ef0c13.icc”: Permission denied
feb. 26 00:08:11 fedora-desktop gsd-color[2050]: failed to set screen _ICC_PROFILE: Failed to open file “/home/zeno/.local/share/icc/edid-ed14a1c8ed95d56b18c24bb372ef0c13.icc”: Permission denied
feb. 26 00:08:12 fedora-desktop gsd-color[3198]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_AOC_AG273QS3R4_255_gdm_42
feb. 26 00:08:34 fedora-desktop pulseaudio[2912]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
░░ Subject: Unit failed
░░ The unit pmie.service has entered the 'failed' state with result 'protocol'.
░░ Subject: A start job for unit pmie.service has failed
░░ The job identifier is 300 and the job result is failed.
feb. 26 00:09:52 fedora-desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pmie comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
feb. 26 00:09:52 fedora-desktop kernel: audit: type=1130 audit(1614294592.818:441): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pmie comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
░░ Subject: Unit failed
░░ The unit pmlogger.service has entered the 'failed' state with result 'protocol'.
░░ Subject: A start job for unit pmlogger.service has failed
░░ The job identifier is 282 and the job result is failed.
feb. 26 00:09:53 fedora-desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pmlogger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
feb. 26 00:09:53 fedora-desktop kernel: audit: type=1130 audit(1614294593.256:446): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pmlogger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
░░ Subject: Unit failed
░░ The unit pmie.service has entered the 'failed' state with result 'protocol'.
░░ Subject: A start job for unit pmie.service has failed
░░ The job identifier is 4378 and the job result is failed.
feb. 26 00:09:53 fedora-desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pmie comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
feb. 26 00:09:53 fedora-desktop kernel: audit: type=1130 audit(1614294593.273:447): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pmie comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
feb. 26 00:09:53 fedora-desktop pcp[11065]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
I think this is the correct part of the journal but I am unsure, since the shutdown process is so fast. If that’s the case, Kerberos Cache Manager seems to be the issue.