solved (was: Re: logging to normal radius.log and syslog)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hey, we start the radiusd in debugging mode and with the following line in rc.local we now just get the loggin attempts into the radius.log: tail -f /var/log/radius/radius_complete.log | grep --line-buffered \:\ Login /var/log/radius/radius.log ca mIke -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbrwKyUY4xkIcFVQRAu/kAJwISuux9C2DjahkQcJ3RBF6a3gjuACg8YUU /Oe091a34P/LLI4TCnJsXhQ= =mA6Y -END PGP SIGNATURE- - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
logging to normal radius.log and syslog
hey @all,
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
We start radiusd with daemontools and with these parameters:
loggeropt=logger -p local6.info -t radiusd -s
ARGS=-Afxyz
NICELEVEL=-10
exec nice -n $NICELEVEL $RADIUSD $ARGS | $loggeropt
this works quite good but there are nomore messages in the radius.log - file.
the radiusd.conf:
15:09:45 Xradius ~ [root]grep radius.log /etc/raddb/radiusd.conf
log_file = ${logdir}/radius.log
the detail logs are working!
any ideas what can I do?
thanks
mIke
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: logging to normal radius.log and syslog
Michael Messner [EMAIL PROTECTED] wrote: for testing we write the complete debugging messages to syslog into a special file but with this method the loggin to the normal radius.log file won't work anymore! Because it's in debugging mode. Output goes to STDOUT, and not to radius.log. any ideas what can I do? Edit the source to make it behave the way you want. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: logging to normal radius.log and syslog
tail -F radius.log | logger
- Original Message -
From: Michael Messner [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, November 16, 2006 3:10 PM
Subject: logging to normal radius.log and syslog
hey @all,
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
We start radiusd with daemontools and with these parameters:
loggeropt=logger -p local6.info -t radiusd -s
ARGS=-Afxyz
NICELEVEL=-10
exec nice -n $NICELEVEL $RADIUSD $ARGS | $loggeropt
this works quite good but there are nomore messages in the radius.log -
file.
the radiusd.conf:
15:09:45 Xradius ~ [root]grep radius.log /etc/raddb/radiusd.conf
log_file = ${logdir}/radius.log
the detail logs are working!
any ideas what can I do?
thanks
mIke
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: logging to normal radius.log and syslog
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan DeKok schrieb: Michael Messner [EMAIL PROTECTED] wrote: for testing we write the complete debugging messages to syslog into a special file but with this method the loggin to the normal radius.log file won't work anymore! Because it's in debugging mode. Output goes to STDOUT, and not to radius.log. sure, we need the possibility to analyze the files any ideas what can I do? Edit the source to make it behave the way you want. not good for me ;) is something like this planed for teh future? I think this would be very helpfull, so it's easy to have a look at the normal log-output and if there are problems it's possible to analyse the debugg log-file! ca mIke -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFXORJyUY4xkIcFVQRApbBAJsHkD51loPMRBGeALQoC52poZ1ZuwCeI1Ge hLy1xOh1GZkuw9Q4MAtQ5xo= =e52w -END PGP SIGNATURE- - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: logging to normal radius.log and syslog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thor Spruyt schrieb:
tail -F radius.log | logger
radius.log is empty!
ca mIke
- Original Message - From: Michael Messner
[EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, November 16, 2006 3:10 PM
Subject: logging to normal radius.log and syslog
hey @all,
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
We start radiusd with daemontools and with these parameters:
loggeropt=logger -p local6.info -t radiusd -s
ARGS=-Afxyz
NICELEVEL=-10
exec nice -n $NICELEVEL $RADIUSD $ARGS | $loggeropt
this works quite good but there are nomore messages in the radius.log
- file.
the radiusd.conf:
15:09:45 Xradius ~ [root]grep radius.log /etc/raddb/radiusd.conf
log_file = ${logdir}/radius.log
the detail logs are working!
any ideas what can I do?
thanks
mIke
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFXOS8yUY4xkIcFVQRAjkIAJ9bPF002gntBWxDZBvjzPLCbWQ1dACdFyKq
gueoUk/BLZl6P+pr9ijByqg=
=dXIR
-END PGP SIGNATURE-
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: logging to normal radius.log and syslog
Michael Messner [EMAIL PROTECTED] wrote: Because it's in debugging mode. Output goes to STDOUT, and not to radius.log. sure, we need the possibility to analyze the files Then why are you running the server in debugging mode, with output goind to STDOUT? I think this would be very helpfull, so it's easy to have a look at the normal log-output and if there are problems it's possible to analyse the debugg log-file! I don't understand what you're trying to do. You want the output to go to STDOUT for debugging, AND to go to radiusd.log? Why? Even that's possible with a simple Unix command: $ radiusd -X | tee /var/log/radius.log This should do what you want. But again, why are you using '-x' if you want the output to go to radius.log? What are you doing with the text being printed to stdout? Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
