#3738 handle stale pid files
Closed: duplicate Opened by pomac.

So, while experiencing a OOM event with a root shell available I noticed that i couldn't restart SSSD after it crashed. Eventually I noticed that SSSD has no concept of stale pid files at all, which is something i find very surprising... This is something that is very common and given how important SSSD is when you run it - I would prefer to have some kind of unix socket to ping the service to make sure that it's actually running and working.

I reported this on irc but noone seemed to react - ended up having to create a account here just to be able to push this bugreport.

See log:
https://pastebin.com/rMMa5TYg

Section of SSSD code not handling stale pidfiles:
https://github.com/SSSD/sssd/blob/master/src/monitor/monitor.c#L2627


Ian,

Firstly, sorry that we're not that responsive on IRC. I understand it's quite hard to get an answer there but, please, do not leave with the impression that we were ignoring the issue. It's just that sometimes our team is really busy with a few different things.

You took the right path about opening an issue, thanks for that.

Secondly, now about this issue, as we ended up discussing on IRC, it's a duplicate of #3617. And as agreed on our IRC talk, I'm closing this one and we can keep the discussion in the #3617.

Metadata Update from @fidencio:
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

It is more likely that it is a duplicate of #3528 which is already fixed in 1.16.1

And here is a hotfix for older downstream version:

  • mkdir /etc/systemd/system/sssd.service.d/
  • echo -e '[Service]\nPIDFile=/var/run/sssd.pid\n' > /etc/systemd/system/sssd.service.d/sssd_pidfile.conf
  • systemctl daemon-reload
  • systemctl restart sssd.service

Metadata Update from @lslebodn:
- Issue status updated to: Open (was: Closed)

Metadata Update from @lslebodn:
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4746

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata