Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1544457
[+] Description of problem: - In an environment where krb5_child.log is rotated, it was found that SSSD continues to write to the rotated log file, despite receiving HUP. [+] Version-Release number of selected component (if applicable): - sssd-1.15.2-50.el7_4.8.x86_64 [+] How reproducible: - Always [+] Steps to Reproduce: 1. # mv /var/log/sssd/krb5_child.log /var/log/sssd/krb5_child.log.old ; /bin/kill -HUP `cat /var/run/sssd.pid 2>/dev/null` 2> /dev/null || true 2. Authenticate using AD/KRB5 SSSD backend. [+] Actual results: - SSSD continues to write logs to /var/log/sssd/krb5_child.log.old [+] Expected results: - SSSD writes logs to /var/log/sssd/krb5_child.log
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1544457
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.2
Careful user mentioned on IRC that this ticket is a duplicate of another older ticket #2679. And they are triaged in different milestones.
Thank you, I closed that one as a duplicate.
Metadata Update from @jhrozek: - Issue priority set to: major
Since we are near the 1.16.2 release and this ticket has no PR yet, it will slip into 1.16.3.
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.3 (was: SSSD 1.16.2)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.4 (was: SSSD 1.16.3)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 1.16.4) - Issue tagged with: bug
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)
Metadata Update from @thalman: - Issue tagged with: bugzilla
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/4667
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.