[RADIATOR] UNS: Re: Best way to log timeout requests

[Dubravko Penezic]

Hi Hugh,

thank you for information. I found it, just to more clarify to others, 
that line is part of RADIATOR log /radiator.log), not authlog handler 
(and that confuse me).

Additional, do you have any example to save that type of information in 
separate file ? :) it will be useful.

Regards,
Dubravko

On 6/14/23 04:05, Hugh Irvine wrote:
> 
> Hello Dubravko -
> 
> Radiator logs timed out proxy requests like this:
> 
> 2b87ecc0 Wed Jun 14 11:59:46 2023 858630: INFO: AuthRADIUS : No reply after 20 seconds and 3 retransmissions to 127.0.0.1 port 1111 for user 'mikem' (233)
> 2b87ecc0 Wed Jun 14 11:59:46 2023 859037: INFO: AuthRADIUS : Could not find a working host to forward user 'mikem' (1) after 20 seconds. Ignoring
> 
> 
> What additional information would you like to see?
> 
> regards
> 
> Hugh
> 
> 
>> On 9 Jun 2023, at 07:45, Dubravko Penezic via radiator <radiator at lists.open.com.au> wrote:
>>
>> Hi,
>>
>> i did try to found in documentation and on Internet but didnt found answer on simple question :) ...
>>
>> How to log timeouted requests on RADIATOR when RADIATOR act like proxy server  ?
>>
>> Basically log is written once request have final state, or state is set by handler, but timeouted request dosnt have finale state.
>>
>> It is "big" issue when you try to "debug" some authentication across of RADIUS hierarchy and a lot of proxy server on a path is RADIATOR instance.
>>
>> For example FreeRADIUS write FAIL in log if request is timeout.
>>
>> Regards,
>> Dubravko
>> _______________________________________________
>> radiator mailing list
>> radiator at lists.open.com.au
>> https://lists.open.com.au/mailman/listinfo/radiator
>