group.of.nepali.translators team mailing list archive

[Robie Basak <1777860@xxxxxxxxxxxxxxxxxx>]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

It looks like upstream added a PIDFile entry to the systemd service
definition in 1.16.1, which is included in Bionic and Cosmic. So it's
likely that this bug is fixed there.

Therefore this bug affects only Xenial and possibly Artful.

> In our environment, with hundreds of computers running Ubuntu, the
'solution' brought forth in that discussion, to investigate and handle
the issue manually, is not a serious option.

Did you know that you can work around the problem by creating an
override file at /etc/systemd/system/sssd.service?

Nevertheless we should fix this in Xenial for the benefit of all other
users who hit this, but now that you know the workaround should stop the
bug affecting you easily enough.

** Also affects: sssd (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: sssd (Ubuntu)
       Status: New => Fix Released

** Changed in: sssd (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: sssd (Ubuntu Xenial)
   Importance: Undecided => Medium

** Tags added: server-next

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1777860

Title:
  Sssd doesn't clean up PIDfile after crash

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Xenial:
  Triaged

Bug description:
  After having crashed, sssd will not start, because the old PIDfile is still present. The fact that the process does not exist any more does not cause the PIDfile to be cleaned up.
  This bug is already known, but not fixed, upstream: https://pagure.io/SSSD/sssd/issue/3528
  (also contains instructions for reproduction).

  In our environment, with hundreds of computers running Ubuntu, the
  'solution' brought forth in that discussion, to investigate and handle
  the issue manually, is not a serious option.

  So I propose that we make systemd handle the PIDfile in case of a
  crash. With the attached one-line patch applied, systemd will clean up
  the PIDfile after a crash. That way, sssd doesn't have to make
  assumptions about namespaces, but the package still handles the issue.

  Mandatory data:

  Ubuntu version:
    Ubuntu 16.04.4 LTS

  Package version:
    apt-cache policy $(dpkg -S /lib/systemd/system/sssd.service )
     sssd-common: Installed: 1.13.4-1ubuntu1.11

  What I expect to happen:
  After
    kill -9 $(cat /var/run/sssd.pid)
  the command
    systemctl start sssd
  results in a running sssd.

  What happens instead:
  No sssd is running. Only after
    rm /var/run/sssd.pid
    systemctl start sssd
  does it run again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1777860/+subscriptions