https://bugzilla.redhat.com/show_bug.cgi?id=2334868
--- Comment #18 from Charalampos Stratakis cstratak@redhat.com --- (In reply to Alexey Tikhonov from comment #17)
(In reply to Charalampos Stratakis from comment #16)
(In reply to Alexey Tikhonov from comment #14)
(In reply to Charalampos Stratakis from comment #9)
[sssd] [access_check_file] (0x0020): Unexpected access to '/etc/sssd/conf.d/ipa.redhat.com.conf' by other users
What is the output of `ls -la /etc/sssd/conf.d/ipa.redhat.com.conf`?
-r--r-----. 1 root sssd
And 'sssd_kcm' still says "Unexpected access to '/etc/sssd/conf.d/ipa.redhat.com.conf' by other users"?
Restarted sssd-kcm and tried to restart sssd as well to see any logs updates if at all as possibly the unexpected access could be from before from tinkering with perms.
So currently my sssd-kcm logs provide: (2025-01-07 18:31:05): [kcm] [server_setup] (0x3f7c0): Starting with debug level = 0x0070 (2025-01-07 18:31:05): [kcm] [activate_unix_sockets] (0x3f7c0): Warning: socket path defined in systemd unit (/run/.heim_org.h5l.kcm-socket) and sssd.conf (/var/run/.heim_org.h5l.kcm-socket) don't match (2025-01-07 18:31:05): [kcm] [server_loop] (0x3f7c0): Entering main loop under uid=963 (euid=963) : gid=963 (egid=963) with SECBIT_KEEP_CAPS = 0 and following capabilities: (nothing)
And the "systemctl status sssd":
× sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf, 50-keep-warm.conf Active: failed (Result: exit-code) since Tue 2025-01-07 18:31:49 CET; 8min ago Invocation: 4e1b18f719f64b7a8260463a95878a97 Process: 259548 ExecStartPre=/bin/chown -f -R root:sssd /etc/sssd (code=exited, status=0/SUCCESS) Process: 259550 ExecStartPre=/bin/chmod -f -R g+r /etc/sssd (code=exited, status=0/SUCCESS) Process: 259552 ExecStartPre=/bin/sh -c /bin/chown -f sssd:sssd /var/lib/sss/db/*.ldb (code=exited, status=0/SUCCESS) Process: 259554 ExecStartPre=/bin/chown -f -R sssd:sssd /var/lib/sss/gpo_cache (code=exited, status=0/SUCCESS) Process: 259556 ExecStartPre=/bin/sh -c /bin/chown -f sssd:sssd /var/log/sssd/*.log (code=exited, status=0/SUCCESS) Process: 259558 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited, status=1/FAILURE) Main PID: 259558 (code=exited, status=1/FAILURE) Mem peak: 6.6M CPU: 174ms
Jan 07 18:31:49 ldap_child[259571]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found Jan 07 18:31:49 ldap_child[259571]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found Jan 07 18:31:49 ldap_child[259571]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found Jan 07 18:31:49 ldap_child[259571]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found Jan 07 18:31:49 ldap_child[259571]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found Jan 07 18:31:49 ldap_child[259571]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab Jan 07 18:31:49 sssd[259558]: Exiting the SSSD. Could not restart critical service [ipa.redhat.com]. Jan 07 18:31:49 systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE Jan 07 18:31:49 systemd[1]: sssd.service: Failed with result 'exit-code'. Jan 07 18:31:49 systemd[1]: Failed to start sssd.service - System Security Services Daemon.
Attaching the latest snippet of /var/log/sssd/sssd.log as well.