Message: 5
Date: Wed, 28 Apr 2010 16:19:30 +0200
From: Alan DeKok <
aland@deployingradius.com>
Subject: Re: Error logs on freeradius 2.1.8
To: FreeRadius users mailing list
<
freeradius-users@lists.freeradius.org>
Message-ID: <
4BD843F2.9030803@deployingradius.com>
Content-Type: text/plain;
charset=ISO-8859-1
Oninz Unix wrote:
> I know some os the thread almost similar to my problem, but let
> me send some logs from my freeradius logs.
>
> Tue Apr 27 17:59:44 2010 : Info: WARNING: Child is hung for request 383.
> Tue Apr 27 17:59:44 2010 : Info: WARNING: Child is hung for request 382.
> Tue Apr 27 17:59:45 2010 : Info: WARNING: Child is hung for request 379.
> Tue Apr 27 17:59:46 2010 : Info: WARNING: Child is hung for request 383.
> Tue Apr 27 17:59:48 2010 : Info: WARNING: Child is hung for request 377.
...
> Error: WARNING: Unresponsive child for request 384, in module
> sql2_redundant component accounting
...
> I hope you could help me were to start to debug and solve the problem.
You have a firewall between the RADIUS server and database. The
firewall is dropping the RADIUS -> database TCP
connections.
I have *no* idea why anyone thinks this is a good idea. The firewall
(if any) should be configured to allow ANY TCP (RADIUS -> DB : port).
But many people create rules allowing only "established" TCP
connections, and then the firewall helpfully loses track of which
sessions are established.
Stop breaking your network.
Alan DeKok.