Free radius : Increase debug log level
Hi All, We are running FreeRADIUS Version 2.1.11 on Red Hat Enterprise Linux Server release 5.10 (Tikanga). We are looking to increase the debug log level to identify the free radius crashing and from the man page we could see the below options. -X Turn on full debugging. -x Turn on additional debugging. (-xx gives more debugging). But the above options are not providing more details of crash error. Is there any other options to increase the logging level (any command line or configuration file change to increase logging level ) ? Thanks in Advance. Regards, Lakshmanji
On 26 May 2014, at 15:51, Lakshmanji Chandrasekaran <lakshmanji.x.chandrasekaran@gsk.com> wrote:
Hi All,
We are running FreeRADIUS Version 2.1.11 on Red Hat Enterprise Linux Server release 5.10 (Tikanga).
We are looking to increase the debug log level to identify the free radius crashing and from the man page we could see the below options.
-X Turn on full debugging. -x Turn on additional debugging. (-xx gives more debugging).
But the above options are not providing more details of crash error.
Is there any other options to increase the logging level (any command line or configuration file change to increase logging level ) ?
No, there is no combination of flags which will cause the server to increase the logging level of the server to the point where it produces a backtrace for 2.1.11. It will do it automatically for 2.2.5 and 3.0.3, but these are not available pre-packed for RHEL 5.10, so you need to talk to RH (who you presumably purchased support from (so why are you asking questions here?!)) to get the support/debugging procedure they want you to use. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Hi,
We are looking to increase the debug log level to identify the free radius crashing and from the man page we could see the below options.
radiusd -X and the, if thats NOT providing enough detail (and it probably wont be) you need to follow the doc/bugs instructions (either available in the source code archive, should be installed in the /usr/share/doc/freeradisu (or somesuch) or is available online https://github.com/FreeRADIUS/www.freeradius.org/blob/master/radiusd/doc/bug... version 3.x of the core has a live hook to allow automatic triggering of debugging tools upon a crash. ...and you say you are running 2.1.11 ? well, I can guarantee you have plenty of bugs - just look at the changelog of the releases since that release - your bug has probably already been fixed - look at running 2.2.5 instead !!) alan
On Mon, May 26, 2014 at 9:51 PM, Lakshmanji Chandrasekaran < lakshmanji.x.chandrasekaran@gsk.com> wrote:
Hi All,
We are running FreeRADIUS Version 2.1.11 on Red Hat Enterprise Linux Server release 5.10 (Tikanga).
We are looking to increase the debug log level to identify the free radius crashing and from the man page we could see the below options.
Doesn't RHEL/Centos5 have 2.1.12 already? http://pkgs.org/centos-5/centos-x86_64/freeradius2-2.1.12-5.el5.x86_64.rpm.h... Your best bet would be to try upgrading RH's latest version first, in case the bug was already fixed. If it still crashed, then contact RH support and report the bug there. If you DON'T have RH support, and would be willing to try anything in order to help diagnose your problem, using unofficial prebuilt packages of latest stable version might help http://software.opensuse.org/download.html?project=home%3Afreeradius%3A2.x.x... Note the different package name (freeradius vs freeradius2), so you can't simply upgrade in-place. A backup-old-config -> uninstall -> install -> restore-config cycle might be necessary. Again, in your case, you should ONLY use this if you DON'T have RH support, can't build your own package, and would be willing to try anything in order to help diagnose your problem. -- Fajar
Hi All, Thanks for responding. The Free radius version is an open source edition being used and not licensed one. Can we get the procedure for going for an upgrade to 2.2.5 version and if that's supported in RHEL 5.10 ? Thanks, Lakshmanji Chandrasekaran From: freeradius-users-bounces+lakshmanji.x.chandrasekaran=gsk.com@lists.freeradius.org [mailto:freeradius-users-bounces+lakshmanji.x.chandrasekaran=gsk.com@lists.freeradius.org] On Behalf Of Fajar A. Nugraha Sent: Monday, May 26, 2014 9:23 PM To: FreeRadius users mailing list Subject: Re: Free radius : Increase debug log level On Mon, May 26, 2014 at 9:51 PM, Lakshmanji Chandrasekaran <lakshmanji.x.chandrasekaran@gsk.com<mailto:lakshmanji.x.chandrasekaran@gsk.com>> wrote: Hi All, We are running FreeRADIUS Version 2.1.11 on Red Hat Enterprise Linux Server release 5.10 (Tikanga). We are looking to increase the debug log level to identify the free radius crashing and from the man page we could see the below options. Doesn't RHEL/Centos5 have 2.1.12 already? http://pkgs.org/centos-5/centos-x86_64/freeradius2-2.1.12-5.el5.x86_64.rpm.h... Your best bet would be to try upgrading RH's latest version first, in case the bug was already fixed. If it still crashed, then contact RH support and report the bug there. If you DON'T have RH support, and would be willing to try anything in order to help diagnose your problem, using unofficial prebuilt packages of latest stable version might help http://software.opensuse.org/download.html?project=home%3Afreeradius%3A2.x.x... Note the different package name (freeradius vs freeradius2), so you can't simply upgrade in-place. A backup-old-config -> uninstall -> install -> restore-config cycle might be necessary. Again, in your case, you should ONLY use this if you DON'T have RH support, can't build your own package, and would be willing to try anything in order to help diagnose your problem. -- Fajar
Hi,
Can we get the procedure for going for an upgrade to 2.2.5 version and if that's supported in RHEL 5.10 ?
just build it the same way as your current version has been built.... the 'make install' should not touch any present file....but its best practice/safer to ensure you have a backup copy of your config anyway so eg cp -R /etc/raddb /etc/raddb.backup before doing the install there are MINIMAL differences between the previous versions and if you havent used any special features it should be a pretty much drop in replacement....however, the general advice is to note down what configuration change you made to the original and then re-enact those on a FRESH clean config (ie check your change log/revisions and then do 'mv /etc/raddb /etc/raddb.backup' instead and then edit the files in the config directory to match your requirements) - in this way you rconfig files have ALL the new options/docs present so you can start using the newer features rather than not knowing about them. for a 2.1.x - 2.2.x this isnt too bad..... the jump to 3.x is quite another thing! ;-) alan
On Tue, May 27, 2014 at 12:09 AM, Lakshmanji Chandrasekaran <lakshmanji.x.chandrasekaran@gsk.com> wrote:
Hi All,
Thanks for responding.
The Free radius version is an open source edition being used and not licensed one.
There is no such thing as licensed version of freeradius. Did you mean you compile it from source (or use centos packages) instead of redhat's RHN?
Can we get the procedure for going for an upgrade to 2.2.5 version and if that's supported in RHEL 5.10 ?
Depends on how you installed the previous version. If you install it from source (e.g. ./configure, make, make install) then Alan's suggestion should work. If you installed it from a repository/RPM (e.g. "yum install"), then read my previous message:
http://software.opensuse.org/download.html?project=home%3Afreeradius%3A2.x.x...
Note the different package name (freeradius vs freeradius2), so you can't simply upgrade in-place. A backup-old-config -> uninstall -> install -> restore-config cycle might be necessary.
The link has instructions on how to add the unofficial repository. I assume you know how to perform file/directories backup/restore and package install/uninstall? If not, then you need to learn about that first (Google is good place to start). FR's config files are located on /etc/raddb. -- Fajar
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Arran Cudbard-Bell -
Fajar A. Nugraha -
Lakshmanji Chandrasekaran