Red Hat Bugzilla – Bug 446864
freeradius is broken
Last modified: 2009-07-15 04:24:16 EDT
Description of problem:
FreeRadius 2.0.2 does not work on a default install of Fedora 9. Specifically,
it seems to fail to look up the default port for radius in /etc/services and
ends up listening on a random UDP port.
Speculation on the FreeRadius list is that this is a bug in gcc related to
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install freeradius
1a. comment out the broken "sql.conf" and "sqlcounter.conf" includes in
2. service radiusd start
3. lsof -i :1812 - returns nothing
4. lsof -p `cat /var/run/radiusd.pid` - shows radiusd listening on random ports
Radius server fails
Radius server works
This can be worked around by changing "port = 0" to "port = 1812" in the listen
sections of radiusd.conf but THIS IS NOT A FIX; gcc seems to be optimising stuff
away that it SHOULD NOT BE
I will attach a trace of a gdb session - you can clearly see the getservbyname
call failing as the return value is optimised away
Created attachment 305691 [details]
Sorry, I omitted the link to the discussion on the FreeRadius list:
Thank you Phil for your work on this. Actually just this morning I became aware
the "FreeRADIUS 2 not listening on right port" thread was actually an F-9 issue.
I do skim the list, but because of the high traffic only read what seems
relevant and had initially skipped this thread. I will immediately investigate.
The short term workaround might be build the package without optimization and
send it out as an update. FYI, my daughter is graduating from college this
weekend and I have family commitments starting this afternoon and continuing
through Tuesday, I'll try to push out a new package before I have to leave
today, but there is an excellent chance it won't happen until I return, I'll see
what I can do.
FWIW, there were no source code changes in our RPM, the only real difference was
in packaging, splitting things up into smaller sub-packages to reduce dependency
bloat, but so far no source code changes have been applied to the 2.0.x series.
freeradius-2.0.3-3.fc9 has been submitted as an update for Fedora 9
I have rebuilt the package without compiler optimization. Due to time
constraints on my end I am unable to test the new package but felt it was
worthwhile to push it out as an update ASAP based on feedback from the list
which confirms building without optimization fixes the problem. Upon my return I
will investigate the root cause of the original problem.
freeradius-2.0.3-3.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
This should not have been automatically closed. I'm re-opening it until we
understand the root cause of the problem and have re-released a package with
I have analyzed the generated machine code for the function fr_socket on i386
with -O2 optimization. It does appear the assignment of the port value in the
saddr_in struct is not generating code. I have created a new bug report against
GCC to track this issues (bug #448743). You may find complete analysis in that
freeradius-2.0.5-1.fc9 has been submitted as an update for Fedora 9
freeradius-2.0.5-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update freeradius'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-5753
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.