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

[A.L.M.Buxey at lboro.ac.uk]

Hi,

only 2 proxies so not UK  ;-)

> # 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. 

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.

alan