afres sssd process crashed and restart users are not able to login

[AlexeySaff]

Hi, quite often have the following situation

● sssd.service - System Security Services Daemon
Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/sssd.service.d
└─override.conf
Active: active (running) since Tue 2026-05-05 15:05:30 IST; 1 month 28 days ago
Main PID: 941 (sssd)
Tasks: 7 (limit: 408494)
Memory: 33.9M (peak: 80.3M)
CPU: 21min 41.422s
CGroup: /system.slice/sssd.service
├─ 941 /usr/sbin/sssd -i --logger=files
├─ 961 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
├─ 962 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files
├─ 963 /usr/libexec/sssd/sssd_ssh --uid 0 --gid 0 --logger=files
├─ 964 /usr/libexec/sssd/sssd_sudo --uid 0 --gid 0 --logger=files
├─ 965 /usr/libexec/sssd/sssd_pac --uid 0 --gid 0 --logger=files
└─1493628 /usr/libexec/sssd/sssd_be --domain int.quantbox.in --uid 0 --gid 0 --logger=files

Jul 03 16:58:06 qb-r39-psr35.int.quantbox.in sssd_be[1492022]: GSSAPI client step 1
Jul 03 16:58:06 qb-r39-psr35.int.quantbox.in sssd_be[1492022]: GSSAPI client step 1
Jul 03 16:58:06 qb-r39-psr35.int.quantbox.in sssd_be[1492022]: GSSAPI client step 1
Jul 03 16:58:07 qb-r39-psr35.int.quantbox.in sssd_be[1492022]: GSSAPI client step 2
Jul 03 16:58:30 qb-r39-psr35.int.quantbox.in sssd[941]: Child [1492022] ('int.quantbox.in':'%BE_int.domain.my') was terminated by own WATCHDOG. Consult corresponding logs to figure out the reason.
Jul 03 16:58:30 qb-r39-psr35.int.quantbox.in sssd_be[1493628]: Starting up
Jul 03 16:58:41 qb-r39-psr35.int.quantbox.in sssd_be[1493628]: GSSAPI client step 1
Jul 03 16:58:41 qb-r39-psr35.int.quantbox.in sssd_be[1493628]: GSSAPI client step 1
Jul 03 16:58:41 qb-r39-psr35.int.quantbox.in sssd_be[1493628]: GSSAPI client step 1
Jul 03 16:58:41 qb-r39-psr35.int.quantbox.in sssd_be[1493628]: GSSAPI client step 2

and after that users are not able to login unless completly restart SSSD

[alexey-tikhonov]

Jul 03 16:58:30 qb-r39-psr35.int.quantbox.in sssd[941]: Child [1492022] ('int.quantbox.in':'%BE_int.domain.my') was terminated by own WATCHDOG. Consult corresponding logs to figure out the reason.

Enable 'debug_level = 9' in the domain section of 'sssd.conf' (or snippet), let the issue happen again, and quote a log snippet from '/var/log/sssd/sssd_$domain.log' right before timestamp when "('int.quantbox.in':'%BE_int.domain.my') was terminated by own WATCHDOG" was reported.

[sumit-bose]

Hi,

which version of SSSD are you using?

bye,
Sumit

[alexey-tikhonov]

which version of SSSD are you using?

Recent versions have automatic re-start by systemd, but still root cause that needs to be fixed is WD, imo.

[AlexeySaff]

we are using the one which comes with Rocky 9.7 (2.9.7) /9.8 (2.9.8)

[AlexeySaff]

Recent versions have automatic re-start by systemd, but still root cause that needs to be fixed is WD, imo. - yes, the main process of SSSD is up, the problem with some childs

we have this quite often but very randomly on different servers. Will try to catch it with debug=9