info: WARNING: Child is hung for request XXXX in component <core> module (2.2.5)

[Jonathan]

> Hi,
>
> only 2 proxies so not UK  ;-)

It is Belgium :)


>> # Match-any/previous DEFAULT realm statement
>> realm "~.+$" {
>> #        pool                    = EDUROAM
>>         auth_pool               = EDUROAM
>>         nostrip
>> }
>
>
> urgh, are you doing other unlang filttering? if not you will be sending all kinds of junk upstream
> which is likely to be dropped/discarded...maybe silently or maybe rejected - either way, you are likely to
> be triggering the status-server far more than needed.

I perform a sanity check with filter_username before sending anything else out.


>
> if you are sending RADISU requests off-site then you have to be wary that other sites may not respond quickly...
> and ensure that any NAS/RADIUSserver timeouts in your pipeline are adjusted accoridngly - expect the
> reponse time to be more than a secnd or 2 - default on some kit is like 2 or 3 seconds...may need to extend
> that to eg 5 seconds otherwise your NAS will retransmit the request (hence duplicates) - also ensure you arent cleaning
> up requests to quickly...or they'll be removed from the system before the response has come back..end therefore fail.
>

We have a the following global parameters:
max_request_time=30
cleanup_delay=5

But override per home-server with max_request_time=5 (i want to reject
proxy requests which take longer then 5 seconds to reply as it's
probably bogus anyway then or just a real terribly slow responding
radius server )


> alan
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html