Best practices for logging in production environment?

[Mohamed Lrhazi]

I see that if run with -X, I see this log:

(23)  } #  authenticate = invalid
(23) Failed to authenticate the user.
(23) Login incorrect (eap: Failed continuing EAP PEAP (25) session. EAP
sub-module failed): [ml623] (from client gu_net_141_161 port 0 cli
02-00-00-00-00-01)
(23) Using Post-Auth-Type Reject
(23) # Executing group from file /etc/freeradius/sites-enabled/default



Is there another variable that hold the "Login incorrect" part of that
message?

where can I see the list of all available variables I could log?

Thanks,
Mohamed.


On Thu, Mar 26, 2015 at 6:14 PM, Mohamed Lrhazi <
Mohamed.Lrhazi at georgetown.edu> wrote:

> I tested adding : %{Module-Failure-Message}
>
> for a wrong password, I get :
>
> Access-Reject: r="eap: Failed continuing EAP PEAP (25) session. EAP
> sub-module failed"
>
> Which is not quite good yet :) I guess I need to learn more about logging
> options...
>
> Thanks a lot,
> Mohamed.
>
>
>
> On Thu, Mar 26, 2015 at 5:54 PM, Mohamed Lrhazi <
> Mohamed.Lrhazi at georgetown.edu> wrote:
>
>> No! really? this should be renamed to EasyRADIUS :)
>>
>> Thanks a lot,
>> Mohamed.
>>
>> On Thu, Mar 26, 2015 at 5:43 PM, Matthew Newton <mcn4 at leicester.ac.uk>
>> wrote:
>>
>>> On Thu, Mar 26, 2015 at 05:12:11PM -0400, Mohamed Lrhazi wrote:
>>> > Of course, when a user is rejected, all I have is some data about where
>>> > they came from, but no hints as to why we rejected them....
>>> >
>>> > How do you guys log in production settings? any examples highly
>>> appreciated.
>>>
>>> Add %{Module-Failure-Message} into your linelog might help?
>>>
>>> Matthew
>>>
>>>
>>> --
>>> 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>
>>> -
>>> List info/subscribe/unsubscribe? See
>>> http://www.freeradius.org/list/users.html
>>
>>
>>
>