The radiusd service could not write the output file created by the raddebug utility. The raddebug utility now sets appropriate ownership to the output file, allowing radiusd to write the output.
Description of problem:
raddebug utility from freeradius package allows capturing of debug output from a running server without (unlike radiusd -X) impacting service availability. Debugging output should be stored to a special logfile, using raddebug, this file is created, but debugging output never appears to make it there.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set the control socket mode to rw (raddb/sites-available/control-socket)
2. Start freeradius server without -X
3. Start raddebug (note: without -t parameter raddebug will exit and delete created debug file in 60 seconds)
4. Send request to freeradius (eg. radtest testuser testpwd localhost 0 testing123)
Debugging information is stored in /var/log/radius/radmin.debug.PID
File is empty
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
The output file is not writable by radiusd.
In /usr/sbin/raddebug:96 we make it group writable but as it's run by root, default group is root, not radiusd. We should change group to radiusd as well.
Here's a patch:
--- raddebug.orig 2013-03-29 10:45:10.615000000 +0100
+++ /usr/sbin/raddebug 2013-03-29 10:47:29.015000000 +0100
@@ -93,6 +93,7 @@
# Truncate the file, and ensure it's writable by radiusd
cp /dev/null $outfile
+chgrp radiusd $outfile
chmod g+w $outfile
I made a pull request with this fix
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.