patch where?: WARNING: Child is hung for request XXXX in component <core> module (2.2.5)
Where can i find the patch as the 2.x.x checkout doesnt contain it yet On Friday, November 21, 2014, Alan DeKok <aland@deployingradius.com> wrote:
Jonathan wrote:
The problem we are having is that whenever a radius proxy server (outside of our control: eduroam national home server) doesn't respond in time, we get the following messages blocking freeradius:
Fri Nov 21 17:02:07 2014 : Error: Internal sanity check failed for child state <= NEW MESSAGE since 2.2.6
That means the following has happened:
- the server proxied a request to a home server - eventually, the server gives up, and uses Post-Proxy-Type Fail - while it's running that, the home server replies.
Fri Nov 21 17:02:07 2014 : Error: Reply from home server A.B.C.D port 1812 - ID: 84 arrived too late for request 11986. Try increasing 'retry_delay' or 'max_request_time' Fri Nov 21 17:02:18 2014 : Error: WARNING: Unresponsive thread 11986 for request 0, in component <core> module Fri Nov 21 17:02:19 2014 : Info: WARNING: Child is hung for request 11986 in component <core> module .
That's wrong... it means that the request isn't being processed through a module, BUT the server core thinks that a thread is still processing it.
Hmm... please try the v2.x.x branch:
https://github.com/FreeRADIUS/freeradius-server/archive/v2.x.x.zip
I've found one thing which makes me go "Huh?"
Hopefully that should fix it.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I've patched it and after a few hours running received this message: Sun Nov 23 15:16:19 2014 : Error: ASSERT FAILED event.c[1311]: request->next_callback != NULL Things don't seem to be ok... On Sun, Nov 23, 2014 at 2:32 AM, Alan DeKok <aland@deployingradius.com> wrote:
Jonathan wrote:
Where can i find the patch as the 2.x.x checkout doesnt contain it yet
It's there now.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Jonathan wrote:
I've patched it and after a few hours running received this message:
Sun Nov 23 15:16:19 2014 : Error: ASSERT FAILED event.c[1311]: request->next_callback != NULL
Hmm... OK. I haven't looked at v2 in detail for about 3 years now. I've gone over the code and pushed a fix for the fix. Alan DeKok.
compiled with additional https://github.com/FreeRADIUS/freeradius-server/commit/72ef924520056f5738aa3... and testing... Hopefully this fixes the issue permanently, I let you know On Sun, Nov 23, 2014 at 3:51 PM, Alan DeKok <aland@deployingradius.com> wrote:
Jonathan wrote:
I've patched it and after a few hours running received this message:
Sun Nov 23 15:16:19 2014 : Error: ASSERT FAILED event.c[1311]: request->next_callback != NULL
Hmm... OK. I haven't looked at v2 in detail for about 3 years now.
I've gone over the code and pushed a fix for the fix.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
This patch only lasted for half an hour uptime before spawning and crashing: Sun Nov 23 17:35:42 2014 : Proxy: Marking home server 193.190.198.33 port 1812 as zombie (it looks like it is dead). Sun Nov 23 17:35:42 2014 : Proxy: Received response to status check 7017 (1 in current sequence) Sun Nov 23 17:35:42 2014 : Proxy: Marking home server 193.190.198.33 port 1812 alive Sun Nov 23 17:35:52 2014 : Error: ASSERT FAILED event.c[553]: (request->child_state == REQUEST_CLEANUP_DELAY) || (request->child_state == REQUEST_DONE) On Sun, Nov 23, 2014 at 5:23 PM, Jonathan <huffelduffel@gmail.com> wrote:
compiled with additional https://github.com/FreeRADIUS/freeradius-server/commit/72ef924520056f5738aa3... and testing...
Hopefully this fixes the issue permanently, I let you know
On Sun, Nov 23, 2014 at 3:51 PM, Alan DeKok <aland@deployingradius.com> wrote:
Jonathan wrote:
I've patched it and after a few hours running received this message:
Sun Nov 23 15:16:19 2014 : Error: ASSERT FAILED event.c[1311]: request->next_callback != NULL
Hmm... OK. I haven't looked at v2 in detail for about 3 years now.
I've gone over the code and pushed a fix for the fix.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Jonathan wrote:
This patch only lasted for half an hour uptime before spawning and crashing:
That's why I like assertions. They cause *known* errors, rather than random unknown later errors.
Sun Nov 23 17:35:42 2014 : Proxy: Marking home server 193.190.198.33 port 1812 as zombie (it looks like it is dead). Sun Nov 23 17:35:42 2014 : Proxy: Received response to status check 7017 (1 in current sequence) Sun Nov 23 17:35:42 2014 : Proxy: Marking home server 193.190.198.33 port 1812 alive Sun Nov 23 17:35:52 2014 : Error: ASSERT FAILED event.c[553]: (request->child_state == REQUEST_CLEANUP_DELAY) || (request->child_state == REQUEST_DONE)
I've pushed a fix. I don't really have time to do much testing for 2.x. So thanks for the feedback. And sorry for the multiple patches. Alan DeKok.
participants (2)
-
Alan DeKok -
Jonathan