On 4 Oct 2013, at 12:00, Alex Sharaz <alex.sha...@york.ac.uk> wrote:

> Hmm
> like these then?
> 
> Fri Oct  4 11:24:12 2013 : Info: WARNING: Child is hung for request 17630 in 
> com
> ponent <core> module <thread>.
> Fri Oct  4 11:24:13 2013 : Info: WARNING: Child is hung for request 17635 in 
> com
> ponent <core> module <thread>.
> Fri Oct  4 11:24:14 2013 : Info: WARNING: Child is hung for request 17634 in 
> com
> ponent <core> module <thread>.
> Fri Oct  4 11:24:17 2013 : Info: WARNING: Child is hung for request 17636 in 
> com
> ponent <core> module <thread>.
> Fri Oct  4 11:24:44 2013 : Info: WARNING: Child is hung for request 17633 in 
> com
> ponent <core> module <thread>.
> Fri Oct  4 11:24:52 2013 : Info: WARNING: Child is hung for request 17635 in 
> com
> ponent <core> module <thread>.
> Fri Oct  4 11:24:53 2013 : Info: WARNING: Child is hung for request 17634 in 
> com
> ponent <core> module <thread>.
> Fri Oct  4 11:24:55 2013 : Info: WARNING: Child is hung for request 17636 in 
> com
> ponent <core> module <thread>.
> 

Those would be the ones.

> Reverted back to 2.2.0 as I never saw these errors with it

If I asked particularly nicely, and promised you a beer at the next networkshop
we were both in attendance at, would you be willing to try git head?

I'll roll a v2.2.2_rc0 if it sweetens the deal any? It'd just be really good to
know that that particular issue was fixed before rolling out 2.2.2 and then
finding it was something else and having to roll 2.2.3 a few weeks later.

-Arran

Arran Cudbard-Bell <a.cudba...@freeradius.org>
FreeRADIUS Development Team

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

Reply via email to