Re: Running RADIUS in permanent debug mode with rotating log
Hi, this is FreeRADIUS list, not general Linux lsit - I'd suggest looking at some guides for the EXACT thing you need eg http://www.cyberciti.biz/faq/linux-unix-formatting-dates-for-display/ (and ensure your escape quotes are the right way around) alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Running RADIUS in permanent debug mode with rotating log
On 3 Oct 2013, at 10:14, wrote: >> How can we run radiusd -x > "logname" such that we have different >> logname for each day? > > Clement, may I suggest a cron job? > > At midnight, move the log, kill and restart the radius server with a new log > in the name? Of course you run the risk of possibly killing any > authentication attempts that happen at that point in time, but... that's > something you need to take into account? Please don't. Use a crontab by all means but just use the main log file and enable additional debugging (-xx). As of 2.2.1 you can use the radmin control socket to reopen the log file handle without restarting the server, or sending a -HUP. It's not just the fact you'll kill any EAP auth sessions in progress, but you'll will clear out any cached entries (rlm_cache), and where proxying is being performed upstream server state will be lost. It's also dangerous in that if someone has messed with the configurations, or overwritten the radiusd/freeradius(debian) binary you'll experience an unexpected migration to the new binary/config on next restart. Arran Cudbard-Bell FreeRADIUS Development Team - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
RE: Running RADIUS in permanent debug mode with rotating log
> How can we run radiusd -x > "logname" such that we have different > logname for each day? Clement, may I suggest a cron job? At midnight, move the log, kill and restart the radius server with a new log in the name? Of course you run the risk of possibly killing any authentication attempts that happen at that point in time, but... that's something you need to take into account? Stefan -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Running RADIUS in permanent debug mode with rotating log
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I really wouldn't recommend running in full debug mode on a production server full time... its only single threaded so if you have to service lots of requests you have an immediate bottleneck. What sort of weird problems are you facing? You know you can run on debug mode for single users or clients via radmin/raddebug ?? If you really want to proceed then you can use eg crontab to run a script which kills all radiusd processes and then starts new debug session with the date in the logfile eg radiusd -X > /var/log/debug-'date +args xxx' Where + args xx is the date string format you require alan Clement Ogedengbe wrote: >Hello, > >We have been having "strange" experiences with our RADIUS service >lately and we thought it would be a good idea to run RADIUS in debug >mode "permanently" to enable us effectively troubleshoot user >complaints. > >How can we run radiusd -x > "logname" such that we have different >logname for each day? > >Clement >- >List info/subscribe/unsubscribe? See >http://www.freeradius.org/list/users.html - -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -BEGIN PGP SIGNATURE- Version: APG v1.0.8 iHkEAREIADkFAlJNM9EyHEFsYW4gQnV4ZXkgKEFsYW4gQnV4ZXkpIDxhLmwubS5i dXhleUBsYm9yby5hYy51az4ACgkQobRdvRSkLC7CfwCgir2zDhH8h4HExwUJ1vB9 820ZXBAAnjvmK6fXtpUpJbEGJDCa8gvkkjMz =KXvy -END PGP SIGNATURE- - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Running RADIUS in permanent debug mode with rotating log
Hello, We have been having "strange" experiences with our RADIUS service lately and we thought it would be a good idea to run RADIUS in debug mode "permanently" to enable us effectively troubleshoot user complaints. How can we run radiusd -x > "logname" such that we have different logname for each day? Clement - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
