https://bugzilla.redhat.com/show_bug.cgi?id=2227057
--- Comment #3 from Lukas Slebodnik <lslebodn(a)redhat.com> ---
(In reply to Buvanesh Kumar from comment #2)
Sure.
அ ~ kinit
kinit: Connection refused while getting default ccache
அ ~ sudo kinit
kinit: Connection refused while getting default ccache
//snip
openat(AT_FDCWD, "/var/lib/sss/pubconf/krb5.include.d/",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 18
newfstatat(18, "", {st_mode=S_IFDIR|0755, st_size=0, ...}, AT_EMPTY_PATH) = 0
getdents64(18, 0x5577d97b4400 /* 2 entries */, 32768) = 48
getdents64(18, 0x5577d97b4400 /* 0 entries */, 32768) = 0
close(18) = 0
read(17, "", 4096) = 0
close(17) = 0
openat(AT_FDCWD, "/etc/krb5.conf.d//kcm_default_ccache", O_RDONLY) = 17
The file is owned by the sssd-kcm package but
அ ~ sudo lsof /var/run/.heim_org.h5l.kcm-socket
/run/.heim_org.h5l.kcm-socket
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc
Output information may be incomplete.
But nobody listen on the UNIX socket.
sssd-kcm is systemd socket activated service so you should se at least systemd
listening on the socket
e.g.
[root@localhost ]# lsof /var/run/.heim_org.h5l.kcm-socket
/run/.heim_org.h5l.kcm-socket
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 62u unix 0x00000000f1674ef5 0t0 27704
/run/.heim_org.h5l.kcm-socket type=STREAM (LISTEN)
and later when sssd-kcm is running something like
[root@localhost ]# lsof /var/run/.heim_org.h5l.kcm-socket
/run/.heim_org.h5l.kcm-socket
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 62u unix 0x00000000f1674ef5 0t0 27704
/run/.heim_org.h5l.kcm-socket type=STREAM (LISTEN)
sssd_kcm 346133 root 3u unix 0x00000000f1674ef5 0t0 27704
/run/.heim_org.h5l.kcm-socket type=STREAM (LISTEN)
Is looks like the sssd-kcm.socket is disabled on your system even though it
should be enabled by default
e.g.
[root@localhost ]# systemctl status sssd-kcm.{socket,service}
● sssd-kcm.socket - SSSD Kerberos Cache Manager responder socket
Loaded: loaded (/usr/lib/systemd/system/sssd-kcm.socket; enabled; vendor
preset: enabled)
Active: active (listening) since Tue 2023-07-18 11:57:37 CEST; 1 week 5
days ago
Triggers: ● sssd-kcm.service
Docs: man:sssd-kcm(8)
Listen: /run/.heim_org.h5l.kcm-socket (Stream)
CGroup: /system.slice/sssd-kcm.socket
Jul 18 11:57:37 localhost.localdomain systemd[1]: Listening on SSSD Kerberos
Cache Manager responder socket.
○ sssd-kcm.service - SSSD Kerberos Cache Manager
Loaded: loaded (/usr/lib/systemd/system/sssd-kcm.service; indirect; vendor
preset: disabled)
Active: inactive (dead) since Mon 2023-07-31 11:37:21 CEST; 18s ago
TriggeredBy: ● sssd-kcm.socket
Docs: man:sssd-kcm(5)
Process: 346132 ExecStartPre=/usr/sbin/sssd --genconf-section=kcm
(code=exited, status=0/SUCCESS)
Process: 346133 ExecStart=/usr/libexec/sssd/sssd_kcm --uid 0 --gid 0
${DEBUG_LOGGER} (code=exited, status=0/SUCCESS)
Main PID: 346133 (code=exited, status=0/SUCCESS)
Jul 31 11:31:50 localhost.localdomain systemd[1]: Starting SSSD Kerberos Cache
Manager...
Jul 31 11:31:51 localhost.localdomain systemd[1]: Started SSSD Kerberos Cache
Manager.
Jul 31 11:31:51 localhost.localdomain sssd_kcm[346133]: Starting up
Jul 31 11:37:21 localhost.localdomain systemd[1]: Stopping SSSD Kerberos Cache
Manager...
Jul 31 11:37:21 localhost.localdomain systemd[1]: sssd-kcm.service: Deactivated
successfully.
Jul 31 11:37:21 localhost.localdomain systemd[1]: Stopped SSSD Kerberos Cache
Manager.
I would recommend to check status of related systemd units
`systemctl status sssd-kcm.{socket,service}`
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2227057
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=rep...