Error: WARNING: Unresponsive child
fellows, we are facing a continuous problems in free-radius server. It had been working fine but lately now an error that it generates as we enable forwarding packets from INFRANET Radius Server to FreeRadius server. freeradius ver 1.1.0 the error that it generates in radius.log file is: Wed Jul 5 17:45:20 2006 : Info: Using deprecated naslist file. Support for this will go away soon. Wed Jul 5 17:45:20 2006 : Info: rlm_exec: Wait=yes but no output defined. Did you mean output=none? Wed Jul 5 17:45:20 2006 : Info: rlm_jradius: configuring jradius server 200.100.96.20:1825 Wed Jul 5 17:45:20 2006 : Info: Ready to process requests. Wed Jul 5 17:50:52 2006 : Error: WARNING: Unresponsive child (id 6) for request 16 Wed Jul 5 17:50:52 2006 : Error: WARNING: Unresponsive child (id 7) for request 17 Wed Jul 5 17:50:52 2006 : Error: WARNING: Unresponsive child (id 4) for request 19 Wed Jul 5 17:50:52 2006 : Error: WARNING: Unresponsive child (id 5) for request 20 Wed Jul 5 17:50:52 2006 : Error: WARNING: Unresponsive child (id 8) for request 21 Wed Jul 5 17:50:52 2006 : Error: WARNING: Unresponsive child (id 10) for request 22 Wed Jul 5 17:50:52 2006 : Error: WARNING: Unresponsive child (id 9) for request 24 Wed Jul 5 17:51:04 2006 : Error: WARNING: Unresponsive child (id 4) for request 25 Wed Jul 5 17:51:04 2006 : Error: WARNING: Unresponsive child (id 7) for request 26 Wed Jul 5 17:51:04 2006 : Error: WARNING: Unresponsive child (id 6) for request 28 Wed Jul 5 17:51:06 2006 : Error: WARNING: Unresponsive child (id 5) for request 35 Wed Jul 5 17:51:07 2006 : Error: WARNING: Unresponsive child (id 10) for request 39 Wed Jul 5 17:51:07 2006 : Error: WARNING: Unresponsive child (id 8) for request 38 Wed Jul 5 17:51:07 2006 : Error: WARNING: Unresponsive child (id 9) for request 42 Wed Jul 5 17:51:19 2006 : Error: WARNING: Unresponsive child (id 7) for request 44 Wed Jul 5 17:51:19 2006 : Error: WARNING: Unresponsive child (id 8) for request 46 Wed Jul 5 17:51:19 2006 : Error: WARNING: Unresponsive child (id 4) for request 48 Wed Jul 5 17:51:20 2006 : Error: WARNING: Unresponsive child (id 10) for request 50 Wed Jul 5 17:51:21 2006 : Error: WARNING: Unresponsive child (id 5) for request 52 Wed Jul 5 17:51:21 2006 : Error: WARNING: Unresponsive child (id 6) for request 56 Wed Jul 5 17:51:22 2006 : Error: WARNING: Unresponsive child (id 9) for request 57 Wed Jul 5 17:51:34 2006 : Error: WARNING: Unresponsive child (id 7) for request 58 Wed Jul 5 17:51:34 2006 : Error: WARNING: Unresponsive child (id 10) for request 59 Wed Jul 5 17:51:34 2006 : Error: WARNING: Unresponsive child (id 6) for request 63 Wed Jul 5 17:51:34 2006 : Error: WARNING: Unresponsive child (id 4) for request 66 Wed Jul 5 17:51:34 2006 : Error: WARNING: Unresponsive child (id 8) for request 68 Wed Jul 5 17:51:36 2006 : Error: WARNING: Unresponsive child (id 5) for request 75 Wed Jul 5 17:51:37 2006 : Error: WARNING: Unresponsive child (id 9) for request 79 Wed Jul 5 17:51:51 2006 : Error: WARNING: Unresponsive child (id 8) for request 81 Wed Jul 5 17:51:51 2006 : Error: WARNING: Unresponsive child (id 7) for request 83 Wed Jul 5 17:51:51 2006 : Error: WARNING: Unresponsive child (id 10) for request 86 Wed Jul 5 17:51:51 2006 : Error: WARNING: Unresponsive child (id 6) for request 88 Wed Jul 5 17:51:51 2006 : Error: WARNING: Unresponsive child (id 5) for request 89 Wed Jul 5 17:51:52 2006 : Error: WARNING: Unresponsive child (id 4) for request 92 Wed Jul 5 17:51:52 2006 : Error: WARNING: Unresponsive child (id 5) for request 90 Wed Jul 5 17:52:04 2006 : Error: WARNING: Unresponsive child (id 9) for request 95 Wed Jul 5 17:52:08 2006 : Error: WARNING: Unresponsive child (id 10) for request 96 Wed Jul 5 17:52:08 2006 : Error: WARNING: Unresponsive child (id 6) for request 98 Wed Jul 5 17:52:09 2006 : Error: WARNING: Unresponsive child (id 7) for request 105 Wed Jul 5 17:52:09 2006 : Error: WARNING: Unresponsive child (id 5) for request 106 Wed Jul 5 17:52:09 2006 : Error: WARNING: Unresponsive child (id 4) for request 111 Wed Jul 5 17:52:09 2006 : Error: WARNING: Unresponsive child (id 6) for request 101 Wed Jul 5 17:52:09 2006 : Error: WARNING: Unresponsive child (id 8) for request 102 Wed Jul 5 17:52:19 2006 : Error: WARNING: Unresponsive child (id 4) for request 113 Wed Jul 5 17:52:19 2006 : Error: WARNING: Unresponsive child (id 9) for request 114 Wed Jul 5 17:52:22 2006 : Error: Dropping conflicting packet from client 202.100.96.21:39779 - ID: 38 due to unfinished request 124 Wed Jul 5 17:52:35 2006 : Error: WARNING: Unresponsive child (id 7) for request 118 ................ we have no clue as what the problem has occured. the other question that i have to ask is that is there a way that the freeradius server acknowledge the main INFRANET radius server (which is forwarding the packets to freeradius server) with OK so that main radius server dont get stuck due to waiting of packets acknowldement from freeradius server? our freeradius server is acting as proxy server for the jradius server that process the interim-update packets. If i have left out any required thing, please do tell me. we request for the earliest response. Regards,
"Farhan Karim" <farhan.karim@gmail.com> wrote:
we are facing a continuous problems in free-radius server. It had been working fine but lately now an error that it generates as we enable forwarding packets from INFRANET Radius Server to FreeRadius server.
INFRANET? What's that?
Wed Jul 5 17:50:52 2006 : Error: WARNING: Unresponsive child (id 6) for request 16
It looks like one of the modules that is handling the request is blocked. Fix that. Alan DeKok.
Alan DeKok wrote:
"Farhan Karim" <farhan.karim@gmail.com> wrote:
we are facing a continuous problems in free-radius server. It had been working fine but lately now an error that it generates as we enable forwarding packets from INFRANET Radius Server to FreeRadius server.
INFRANET? What's that?
I believe it's the new and very very stupid name for a Juniper (Funk-based?) product that checks your AV definitions are up to date before letting you through the firewall using either 802.1x or eap-over-udp maybe? With I believe some PEAP extensions. It's probably XML-based. Because, you know, tunnelling XML over EAP over Radius is clearly a good idea. Wow. Such technology. Who could have imagined it. Idiots... If you want a laugh, the marketing literature reads like it was written by someone with severe cognitive problems. "With VPNs came all kinds of problems! But we solved that with our SSL VPN thing. But then it turned out it wasn't solved! We've solved it again with our even more intrusive and proprietary endpoint posture enforcement policy access control definition gateway thing! Yes, you too can make your PCs sit up straight, and rap them across the knuckles with a ruler if they don't. What's that - are we making all these words and terms up without reference to the existing corpus of the English language? Why yes, we are."
Phil Mayers <p.mayers@imperial.ac.uk> wrote:
I believe it's the new and very very stupid name for a Juniper (Funk-based?)
Yes. Juniper bought Funk.
product that checks your AV definitions are up to date before letting you through the firewall using either 802.1x or eap-over-udp maybe?
Like NAC. Which is a little odd from a security perspective. Alan DeKok.
participants (3)
-
Alan DeKok -
Farhan Karim -
Phil Mayers