| Summary: | freeradius logrotate script does not reload running daemon, causing log files not written after logrotate | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Karel Srot <ksrot> |
| Component: | freeradius2 | Assignee: | John Dennis <jdennis> |
| Status: | CLOSED ERRATA | QA Contact: | Patrik Kis <pkis> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 | CC: | dpal, jdennis, j.s.peatfield, pkis, scheunemann |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 705723 | Environment: | |
| Last Closed: | 2013-01-08 05:10:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 807971 | ||
|
Description
Karel Srot
2012-02-03 07:51:24 UTC
I have to second that bug report. After installing "freeradius2-2.1.12-3.el5" on a x86_64 RHEL 5 system the radiusd logrotate stopped working. But it is even worse. Sending a HUP to the "radiusd" will not switch to the newly created logfile. I had to switch to "copytruncate" in "/etc/logrotate.d/radiusd" to get something "working". *** Bug 821567 has been marked as a duplicate of this bug. *** Re comment #2 For me just adding a "/sbin/service radiusd reload" in a postrotate section seems to case radiusd to re-open the log file. This is with freeradius2-2.1.12-3.el5 though my logrotate.d/radiusd entry has a few other tweaks in it as well so maybe those are what is saving us from whatever was causing it not to re-open the log file for you... -- Jon Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0134.html |