Broadcast message from systemd-journald@CtrlAltReboot (Thu 2022-05-12 11:06:54 CEST):
sssd_kcm[7792]: Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No such file or directory]
$ rpm -qi sssd
Name : sssd
Version : 2.7.0
Release : 1.fc36
Architecture: x86_64
Install Date: Mon 25 Apr 2022 08:30:38 BST
Group : Unspecified
Size : 35147
License : GPLv3+
Signature : RSA/SHA256, Thu 14 Apr 2022 20:27:09 BST, Key ID 999f7cbf38ab71f4
Source RPM : sssd-2.7.0-1.fc36.src.rpm
Build Date : Thu 14 Apr 2022 20:11:45 BST
Build Host : buildhw-x86-14.iad2.fedoraproject.org
Packager : Fedora Project
Vendor : Fedora Project
URL : https://github.com/SSSD/sssd/
Bug URL : https://bugz.fedoraproject.org/sssd
Summary : System Security Services Daemon
Description :
Provides a set of daemons to manage access to remote directories and
authentication mechanisms. It provides an NSS and PAM interface toward
the system and a pluggable back end system to connect to multiple different
account sources. It is also the basis to provide client auditing and policy
services for projects like FreeIPA.
The sssd subpackage is a meta-package that contains the daemon as well as all
the existing back ends.
Does the file exist? Can you check its permissions etc? This is what I get, for example:
$ sudo ls -lash /var/log/sssd/
total 12K
0 drwxr-x---. 1 root root 114 May 1 00:01 .
0 drwxr-xr-x. 1 root root 1.1K May 8 00:01 ..
4.0K -rw-------. 1 root root 90 May 12 09:48 sssd_kcm.log
4.0K -rw-------. 1 root root 175 Apr 27 09:21 sssd_kcm.log-20220426.gz
4.0K -rw-------. 1 root root 520 May 12 07:55 sssd_kcm.log-20220501
If the permissions are wrong, we can correct that. If the file doesn’t exist, I guess we can create it too and see if that helps.