2 Jul
2013
2 Jul
'13
2:03 p.m.
On 2 Jul 2013, at 18:51, Alan DeKok <aland@deployingradius.com> wrote:
Ti Leggett wrote:
I'm not sure how the script could be blocking the server after it's already ran and returned the updated packet so the proxying can take place which does happen:
I don't know. All I know is that the default configuration doesn't have child threads blocking when sending Access-Reject.
The problem is due to a local change on your system.
There was a bug in rlm_perl which caused it to go into an infinite loop processing reply attributes. Check if radiusd is using 100% cpu, if it is, upgrade. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team