Understanding debugging logs
D.J.Hartburn at kent.ac.uk
Thu Oct 29 17:37:37 CET 2015
Thanks for all the advice. Is that a device and conquer approach? All
you need to know is if the error is in the top or bottom half then you
can throw half away ;)
I do have an auth problem at the moment, so I'll generate lots of debug
and see where I can get.
On 23/10/15 16:43, Matthew Newton wrote:
> On Fri, Oct 23, 2015 at 03:35:16PM +0000, David Aldwinckle wrote:
>> I find that the easiest way to read the logs is to start with the
>> request, and trace it down from there. Some things I check for:
> On Fri, Oct 23, 2015 at 04:40:20PM +0100, Matthew Newton wrote:
>> I start at the bottom and work up.
> There you go - you've got both options now!
> Start a new trend. Look at a packet somewhere in the middle and
> work out from there.
> p.s. Confession: I occasionally start at the top.
More information about the Freeradius-Users