Description of problem: Current version of freeradius2 does not produce core dump file on segfault. Version-Release number of selected component (if applicable): freeradius2-2.1.7-7.el5.x86_64 How reproducible: Always Steps to Reproduce: 1. Set "allow_core_dumps = yes" in radiusd.conf 2. Comment out "user = radiusd" and "group = radiusd" 3. ulimit -c 1000000000 Actual results: No core dumps are generated on segfault Expected results: core dump file Additional info: This is bug in upstream version. In 2.1.8 it is fixed. Line in changelog: * Enabled "allow_core_dumps" to work again
I don't have the exact same problem, but do have a serious problem with Freeradius2, which too is fixed in 2.1.8. The current release of RedHat freeradius needs to be upgraded. Problem and response from Freeradius developer: ========================== > We are running Freeradius 2.1.7 (on CentOS 5 - freeradius2-2.1.7-7.el5), > and are seeing many of these messages in our log files: > > Fri Jun 11 11:44:19 2010 : Error: Failed binding to proxy address * > port 1815: Address already in use > > The server is already running and so would already be bound to the port, > so why is it trying to bind to it again? These seem to occur initially > in ones or twos, but eventually the server stops responding completely > to requests. At that point we have to restart the radiusd process. > > Is this known about and maybe fixed in 2.1.9? Or is something else going > on here? Changelog from 2.1.8: * Proxying large numbers of packets no longer gives error "unable to open proxy socket". ========================== This is from the freeradius user s mailing list, Subject line "FR 2.1.7: Error: Failed binding to proxy address". This problem is seriously affecting our RADIUS service, so needs to be sorted out soon. John.
Let us track the original issue here. I have forked a separate bug for the issue described in comment #1. https://bugzilla.redhat.com/show_bug.cgi?id=609633
We are not planning to rebase the freeradius2 package in 5.6 release. If you need this specific fix please log a case with customer support and we will try to extract and back port the solution for it. In this case it will be delivered as an errata.
This has been fixed in the current upstream version. Since we are planning on rebasing freeradius2 to the current version in RHEL 5.8 we should automatically pick up the fix in the rebase. This is the git commit to the upstream git repo which addressed this problem: git://git.freeradius.org/freeradius-server.git commit 2967714b702ba960cb716fac8e27551a12fe9d45 Author: Alan T. DeKok <aland> Date: Tue May 4 14:36:42 2010 +0200 Enable core dumps after suid_down A full discussion of the issue and it's resolution can be found here: http://freeradius.1045715.n5.nabble.com/cannot-get-core-dump-of-crashing-freeradius-td2789170.html
Created attachment 541765 [details] test script
Created attachment 541950 [details] test script
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-0196.html