Hello all, Making good progress learning Freeradius. With your help, my new server is running and authenticating now. However, we are used to being able to see logs of all activity (tail -f logfile). With Freeradius, nothing is being written to the logs unless there is a problem. How can I get the logs to show the same stuff that scrolls when Freeradius is in debug mode? That's the level of detail we're used to seeing in the logs. Thanks, Cliff
Cliff Hayes wrote:
Hello all,
Making good progress learning Freeradius. With your help, my new server is running and authenticating now. However, we are used to being able to see logs of all activity (tail -f logfile). With Freeradius, nothing is being written to the logs unless there is a problem. This is the normal behavior. You can add additional auth-related logging using these variables in radiusd.conf:
log_auth = yes log_auth_badpass = yes log_auth_goodpass = yes
How can I get the logs to show the same stuff that scrolls when Freeradius is in debug mode? That's the level of detail we're used to seeing in the logs.
I'm really not sure if this is possible because when you using the debugging command line options it tells the server to print them to stderr. I'm not aware of any command line options that can change this. You could always redirect the output. radiusd -xxx &> radius.log & Chris Carver Network Engineer
Chris, All of those 3 options you mentioned were already set. What else could be wrong? Cliff -----Original Message----- From: freeradius-users-bounces+chayes=afo.net@lists.freeradius.org [mailto:freeradius-users-bounces+chayes=afo.net@lists.freeradius.org]On Behalf Of Chris Carver Sent: Friday, June 09, 2006 9:33 AM To: FreeRadius users mailing list Subject: Re: Logging Cliff Hayes wrote:
Hello all,
Making good progress learning Freeradius. With your help, my new server is running and authenticating now. However, we are used to being able to see logs of all activity (tail -f logfile). With Freeradius, nothing is being written to the logs unless there is a problem. This is the normal behavior. You can add additional auth-related logging using these variables in radiusd.conf:
log_auth = yes log_auth_badpass = yes log_auth_goodpass = yes
How can I get the logs to show the same stuff that scrolls when Freeradius is in debug mode? That's the level of detail we're used to seeing in the logs.
I'm really not sure if this is possible because when you using the debugging command line options it tells the server to print them to stderr. I'm not aware of any command line options that can change this. You could always redirect the output. radiusd -xxx &> radius.log & Chris Carver Network Engineer - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Friday 09 June 2006 10:57, Cliff Hayes wrote:
Chris,
All of those 3 options you mentioned were already set. What else could be wrong?
Cliff
Add this to radiusd.conf: debug_level = 2 (or 3) Debug level 2 gives you the same output as -xx, level 3 gives even more output (and timestamps!). Kevin Bonner
Kevin, Tried that. Unfortunately, it acts like starting radiusd with the -x option, which scrolls all output to the screen. I use Fedora 5 with radiusd configured as a service, so when I do "service radiusd start", it starts scrolling to the screen. There will not usually be a terminal window dedicated to this box. Also, attempting to stop the scrolling (CTL-C) also terminates the radiusd process. What I really need is for the data to go to the log file. log_auth_goodpass = yes does not appear to work for me for some reason. Cliff -----Original Message----- From: freeradius-users-bounces+chayes=afo.net@lists.freeradius.org [mailto:freeradius-users-bounces+chayes=afo.net@lists.freeradius.org]On Behalf Of Kevin Bonner Sent: Friday, June 09, 2006 10:38 AM To: FreeRadius users mailing list Subject: Re: Logging On Friday 09 June 2006 10:57, Cliff Hayes wrote:
Chris,
All of those 3 options you mentioned were already set. What else could be wrong?
Cliff
Add this to radiusd.conf: debug_level = 2 (or 3) Debug level 2 gives you the same output as -xx, level 3 gives even more output (and timestamps!). Kevin Bonner
On Friday 09 June 2006 12:01, Cliff Hayes wrote:
Kevin,
Tried that. Unfortunately, it acts like starting radiusd with the -x option, which scrolls all output to the screen. I use Fedora 5 with radiusd configured as a service, so when I do "service radiusd start", it starts scrolling to the screen. There will not usually be a terminal window dedicated to this box. Also, attempting to stop the scrolling (CTL-C) also terminates the radiusd process. What I really need is for the data to go to the log file. log_auth_goodpass = yes does not appear to work for me for some reason.
Cliff
D'oh! I've only ever used that config option when running on the CLI, mainly to continue debugging output after a HUP. I doubt you can do what you want without code changes. Kevin Bonner
But but but... Why doesn't log_auth_goodpass work for me? Does it work for you? This kind of stuff always happens to me (excuse burst of self-pity). -----Original Message----- From: freeradius-users-bounces+chayes=afo.net@lists.freeradius.org [mailto:freeradius-users-bounces+chayes=afo.net@lists.freeradius.org]On Behalf Of Kevin Bonner Sent: Friday, June 09, 2006 2:04 PM To: FreeRadius users mailing list Subject: Re: Logging On Friday 09 June 2006 12:01, Cliff Hayes wrote:
Kevin,
Tried that. Unfortunately, it acts like starting radiusd with the -x option, which scrolls all output to the screen. I use Fedora 5 with radiusd configured as a service, so when I do "service radiusd start", it starts scrolling to the screen. There will not usually be a terminal window dedicated to this box. Also, attempting to stop the scrolling (CTL-C) also terminates the radiusd process. What I really need is for the data to go to the log file. log_auth_goodpass = yes does not appear to work for me for some reason.
Cliff
D'oh! I've only ever used that config option when running on the CLI, mainly to continue debugging output after a HUP. I doubt you can do what you want without code changes. Kevin Bonner
On Friday 09 June 2006 15:51, Cliff Hayes wrote:
But but but... Why doesn't log_auth_goodpass work for me? Does it work for you? This kind of stuff always happens to me (excuse burst of self-pity).
I'd say to check the value of that option when running in debug mode. On my radius testing server running 1.1.2, it works fine. Kevin Bonner
Not sure how to "check the value of that option when running in debug mode" as you mentioned. I started radiusd -x, but it doesn't list any options. -----Original Message----- From: freeradius-users-bounces+chayes=afo.net@lists.freeradius.org [mailto:freeradius-users-bounces+chayes=afo.net@lists.freeradius.org]On Behalf Of Kevin Bonner Sent: Friday, June 09, 2006 3:24 PM To: FreeRadius users mailing list Subject: Re: Logging On Friday 09 June 2006 15:51, Cliff Hayes wrote:
But but but... Why doesn't log_auth_goodpass work for me? Does it work for you? This kind of stuff always happens to me (excuse burst of self-pity).
I'd say to check the value of that option when running in debug mode. On my radius testing server running 1.1.2, it works fine. Kevin Bonner
On Monday 12 June 2006 13:38, Cliff Hayes wrote:
Not sure how to "check the value of that option when running in debug mode" as you mentioned. I started radiusd -x, but it doesn't list any options.
The lower-case x gives minimal output. The extended debug mode (-X) will print out the config options and their values. Kevin Bonner
participants (3)
-
Chris Carver -
Cliff Hayes -
Kevin Bonner