Hi,
> (2022-07-21 7:11:14): [sssd] [svc_child_info] (0x0020): Child [984]
('abba.xx.priv.yy':'%BE_abba.xx.priv.yy') was terminated by own WATCHDOG
-- this means corresponding process - `sssd_be --domain abba.xx.priv.yy`
in this case - was blocked too long on 'something' (longer than 3*timeout
What log level are you running? I'm also seeing random sssd halts but not
seeing a dump. It looks like sssd recycles from systemd every 15 minutes. It
usually is restarted in 0.1 seconds. But occasionally it doesn't restart until
the next 15 minute cycle. That causes logins and cron jobs to fail
cc'ing the sssd users list.
rob
lejeczek via FreeIPA-users wrote:
> Hi guys.
>
> One of the masters started recently to find SSSD dead and says the
> killer is the WATCHDOG - but I'm not sure about that.
> From sssd.log:
> ...
> ** BACKTRACE DUMP ENDS HERE
> *
The issue is created by sssd.
Instead of re-installing freeipa, I did the below work-around:
Temporarily backup /var/lib/sss/pubconf /var/lib/sss/pubconf_bkp
ssh again to the remote machine. This will update the new hostkey.
Move back /var/lib/sss/pubconf_bkp to /var/lib/sss/pubconf
Now try aga
The issue is created by sssd.
Instead of re-installing freeipa, I did the below work-around:
Temporarily backup /var/lib/sss/pubconf /var/lib/sss/pubconf_bkp
ssh again to the remote machine. This will update the new hostkey.
Move back /var/lib/sss/pubconf_bkp to /var/lib/sss/pubconf
Now try aga
