Public bug reported:

Ubuntu 26.04, sssd-common 2.12.0-1ubuntu5.5.

Since 2.12.0-1ubuntu3 (LP: #2139337), sssd runs as user sssd and writes
its PID file to /run/sssd/sssd.pid. /etc/logrotate.d/sssd-common still
has the path from Debian, which builds with --with-pid-path=/run:

kill -HUP cat /var/run/sssd.pid > /dev/null 2>&1 || true

That file doesn’t exist, so sssd never gets SIGHUP after rotation and
keeps writing to the rotated file. On one host, sssd<domain>.log was
rotated on 2026-11-08, and sssd kept writing to sssd<domain>.log.1 until
it was restarted on 2026-11-12. Once delaycompress compresses .1, sssd
writes into a deleted file. logrotate also prints “cat:
/var/run/sssd.pid: No such file or directory” once per log file, because
there’s no sharedscripts; “|| true” hides it.

Upstream’s src/examples/logrotate.in uses @pidpath@/sssd.pid,
sharedscripts and “su @SSSD_USER@ @SSSD_USER@”, which would fix this.
Possibly related: LP: #2158645.

** Affects: sssd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2174433

Title:
  logrotate config reads /var/run/sssd.pid, but sssd on 26.04 writes
  /run/sssd/sssd.pid

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to