#332 Support logrotate for SSSD DEBUG logs
Closed: Fixed None Opened 14 years ago by sgallagh.

Currently, our DEBUG logs can grow very large. We need to support logrotate managing them.

This means that we need to support listening for the SIGHUP signal. When it is received, we need to close and reopen our logfiles.


This one works for me.

# cat /etc/logrotate.d/sssd 
/var/log/sssd/*log {
    notifempty
    missingok
    postrotate
        /sbin/service sssd condrestart 2> /dev/null > /dev/null || true
    endscript
}

The problem with this approach is that it requires restarting the SSSD service, which can terminate requests in-progress at the time.

The goal of this ticket is to support closing and reopening the files from within the SSSD process itself, so that processing is never interrupted.

Fields changed

owner: sgallagh => jhrozek

Fixed by 71cd2f7 and 5db6de6

doc: 0 => 1
fixedin: => 1.1.0
resolution: => fixed
status: new => closed

Fields changed

tests: 1 => 0
testsupdated: 0 => 1

Documentation update

SSSD will now rotate the logs either automatically as specified in the packaged logrotate config file or manually upon receiving SIGHUP.

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.1

7 years ago

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

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata