On 2 Jul 2013, at 19:28, Ti Leggett <leggett@mcs.anl.gov> wrote:
I'm not seeing a spin lock, but I'm running a 2.2.1 branch version that I believe you pointed me at to fix an rlm_krb5 issue I was seeing earlier this year. Is there an update for that branch or should I be moving to some other version/branch?
On Jul 2, 2013, at 1:03 PM, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
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.
Then it's not the same issue. Break out GDB, set relevant breakpoints, and see where it's hanging, that's all I can suggest. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team