Understanding debugging logs

Matthew Newton mcn4 at leicester.ac.uk
Fri Oct 23 17:40:20 CEST 2015

On Fri, Oct 23, 2015 at 04:15:59PM +0100, David Hartburn wrote:
> Is there any advised technique or tools out there to help understanding
> FreeRADIUS debugging output generated by radmin/raddebug?

Eyes :)

> If not, is the best method working backwards, checking for errors in each
> packet log? I am already filtering by MAC or User-Name to make sure I just
> have output from the session I want.

I start at the bottom and work up.

Find the error, then look back to find why that error occurred.

After a few times doing this you'll work out the bits to skip
pretty quickly.

> This is not a complaint. We are currently moving from NPS so having useful
> debugging is brilliant and a whole new world where problems seem solvable!
> I'm always interested in anything that will make life easier though :)

Experience helps, but I admit the volume of debugs does look
daunting to begin with. But it's pretty much all relevant. Which
is why most questions to this list without debug output result in
"provide the debug output", and few questions that include the
debug output result in requests for further information.

Network RADIUS provide a debug highlighter if that's your thing.




Matthew Newton, Ph.D. <mcn4 at le.ac.uk>

Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom

For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>

More information about the Freeradius-Users mailing list