Additional finding: fixing the PID path alone isn’t enough on Ubuntu.
The responders are socket-activated (sssd-nss.socket, sssd-pam.socket,
sssd-autofs.socket, sssd-pac.socket, …), so sssd_nss, sssd_pam etc. are
children of PID 1, not of the sssd monitor. A SIGHUP to the monitor only
reaches sssd and sssd_be. On a 26.04 host, sssd_nss.log and sssd_pac.log
were rotated at 00:13, and those responders kept writing to the .log.1
files until sssd was restarted at 19:09. This part also affects 24.04
(sssd 2.9.4-1.1ubuntu6.x), where the PID path is correct but the
responders are socket-activated too.

(The postrotate line in the description lost its backticks; it is: kill
-HUP cat /var/run/sssd.pid > /dev/null 2>&1 || true)

Every sssd daemon handles SIGHUP by reopening its logs (te_server_hup in
src/util/server.c), so this postrotate works for both releases:

sharedscripts
postrotate
    pkill -HUP -x 'sssd|sssd_(be|nss|pam|autofs|pac|ssh|sudo|ifp|kcm)' || true
endscript

Tested on 26.04 (2.12.0-1ubuntu5.5): after a forced rotation, sssd,
sssd_be, sssd_nss, sssd_pam and sssd_autofs kept their PIDs and all
write to the new log files.

-- 
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