-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-8.3.0
-
sssd-2.9.4-1.el8
-
None
-
Low
-
rhel-idm-sssd
-
ssg_idm
-
20
-
21
-
0
-
QE ack, Dev ack
-
False
-
False
-
-
None
-
None
-
Pass
-
-
Enabled
-
Automated
-
If docs needed, set a value
-
-
All
-
None
-
57,005
Description of problem:
logfile rotation for sssd_kcm not working properly, sssd_kcm never receives a 'kill -HUP'
Version-Release number of selected component (if applicable):
Affects all sssd/sssd_kcm versions
How reproducible:
always
Steps to Reproduce:
1. dnf -y install sssd sssd_kcm
2. initiate a log rotation via logrotate
Actual results:
File /var/log/sssd/sssd_kcm.log is moved to
/var/log/sssd/sssd_kcm.log.1, but sssd_kcm keeps the file handle on that
file open instead of starting to write to /var/log/sssd/sssd_kcm.log.
Expected results:
sssd_kcm should drop all file handles to /var/log/sssd/sssd_kcm.log.1 and start
writing to /var/log/sssd/sssd_kcm.log
Additional info:
- As part of package sssd, we deploy /etc/logrotate.d/sssd
- that config file leads to
a) /var/log/sssd/*.log being moved to $file.1
b) and then does kill -HUP `cat /var/run/sssd.pid 2>/dev/null`
That is fine for all children of sssd, but as sssd_kcm is a separate
process, it is not notified and never drops the file handle.
- external trackers
- links to
-
RHBA-2023:121691 sssd bug fix and enhancement update
- mentioned on