RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 705723 - freeradius logrotate script does not reload running daemon, causing log files not written after logrotate
Summary: freeradius logrotate script does not reload running daemon, causing log files...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: freeradius
Version: 6.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: John Dennis
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On:
Blocks: 821567
TreeView+ depends on / blocked
 
Reported: 2011-05-18 09:29 UTC by Fajar A. Nugraha
Modified: 2018-11-28 20:18 UTC (History)
5 users (show)

Fixed In Version: freeradius-2.1.12-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: freeradius logrotate script fails to reload the radiusd daemon after a log rotation. Consequence: freeradius log messages are lost after a log rotation. Fix: Add command to freeradius logrotate script to reload radiusd daemon. Result: After a log rotate the radiusd daemon reinitializes and reopens it's log files, log messages are captured.
Clone Of:
: 787111 821567 (view as bug list)
Environment:
Last Closed: 2012-06-20 14:05:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0881 0 normal SHIPPED_LIVE freeradius bug fix and enhancement update 2012-06-19 20:47:36 UTC

Description Fajar A. Nugraha 2011-05-18 09:29:42 UTC 
Description of problem:

RHEL6's freeradius comes with logrotate config file on /etc/logrotate.d/radiusd. A part of it:

/var/log/radius/radius.log {
        monthly
        rotate 4
        create
        missingok
        compress
}

It does not reload running daemon on logrotate, which worked fine for freeradius < 2.1.9. However the behavior changed on 2.1.9. Now it needs to reload (kill -HUP) the running daemon for it to reopen the log file.


Version-Release number of selected component (if applicable):
freeradius-2.1.9-3.el6.x86_64 (latest official non-beta version)
same thing happens when using latest test version from https://bugzilla.redhat.com/show_bug.cgi?id=689045


How reproducible:
Always

Steps to Reproduce:
1. Enable auth logging on radiusd.conf
2. Start freeradius
3. Test auth with radtest
4. Look at /var/log/radius/radius.log -> auth attempt recorded
5. Force logrotate with "logrotate -v -f /etc/logrotate.d/radiusd
6. Re-test auth with readtest
7. Look at /var/log/radius/radius.log
  
Actual results:
Second auth attempt not logged


Expected results:
Second auth attempt logged


Additional info:
Relevant debian bug entry:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602815
Comment 4 Karel Srot 2012-02-03 07:41:02 UTC 
bug present also in freeradius-2.1.10-5.el6
Comment 6 RHEL Program Management 2012-02-08 07:03:31 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.
Comment 10 John Dennis 2012-04-24 17:12:19 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause:

freeradius logrotate script fails to reload the radiusd daemon after a log rotation.

Consequence:

freeradius log messages are lost after a log rotation.

Fix:

Add command to freeradius logrotate script to reload radiusd daemon.

Result:

After a log rotate the radiusd daemon reinitializes and reopens it's log files, log messages are captured.
Comment 11 Jonathan Peatfield 2012-05-15 00:06:31 UTC 
Obviously the same fix is needed for the RHEL5 version of freeradius2, ie
freeradius2-2.1.12-3.el5 as in el5.8

Luckily we noticed pretty quickly and so only lost a couple of day's logs (over the weekend).
Comment 13 errata-xmlrpc 2012-06-20 14:05:43 UTC 
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/RHBA-2012-0881.html
Note You need to log in before you can comment on or make changes to this bug.