I seem to be having the same issue.. seems to happen randomly about once a
week on a production server running a simple perl backend for authentication.
snippet of log...
Thu Nov 14 15:26:38 2002 : Error: WARNING: Unresponsive child (id 65559)
for request 13464
Thu Nov 14 15:26:38 2002 : Error
:
Heya!
I used freeradius 0.7.1 and postgresql 7.1.3, freebsd 4.4-STABLE
Radius began to hang up (if started with -X) or just core dump.
Mon Oct 28 19:40:01 2002 : Error: WARNING: Unresponsive child (id
135801856) for request 29
Mon Oct 28 19:40:06 2002 : Error: WARNING
Igor Chen [EMAIL PROTECTED] wrote:
The main reason of core dumping was delay after sending request to
database. Trigger on UPDATE became too slow (UPDATE request was handled
~40 - 60 sec.)
This problem should be addressed in the documentation in flaming
letters 10 feet high. If the back-end
Of course i understand that :)
I didn't even try to accuse radius developers, but IMHO sql
back-end should give any glue (debugging info) to let the administrator
solve the problem.
On Wed, 30 Oct 2002, Alan DeKok wrote:
Igor Chen [EMAIL PROTECTED] wrote:
The main reason of core dumping was
On Mon, 28 Oct 2002, Igor Chen wrote:
Heya!
I used freeradius 0.7.1 and postgresql 7.1.3, freebsd 4.4-STABLE
Radius began to hang up (if started with -X) or just core dump.
Mon Oct 28 19:40:01 2002 : Error: WARNING: Unresponsive child (id
135801856) for request 29
Mon Oct 28 19:40:06 2002
Heya!
I used freeradius 0.7.1 and postgresql 7.1.3, freebsd 4.4-STABLE
Radius began to hang up (if started with -X) or just core dump.
Mon Oct 28 19:40:01 2002 : Error: WARNING: Unresponsive child (id
135801856) for request 29
Mon Oct 28 19:40:06 2002 : Error: WARNING: Unresponsive child (id
Kostas Kalevras [EMAIL PROTECTED] wrote:
My search filter is: filter = ((objectClass=posixAccount)(uid=%u))
It will work with freeRADIUS 0.7.1 but will not work with the current CVS
(radiusd: FreeRADIUS Version 0.8-pre, for host i686-pc-linux-gnu, built on
Sep 15 2002 at 09:52:08)
AccStop channel #1
- response 64
== WARNING: Unresponsive child (id 2051) for request 61
--
The only problem is the 99%-process that is left over after that sequence.
Everything else is ok: Both connections were recorded completely by the
accunting DB, the user could use
Marco Steinacher [EMAIL PROTECTED] wrote:
I think the problem is not the authentication process. It occurs after a
accounting stop request.
Same thing. Why the heck would it take 60 seconds to log an
accounting request?
The sequence above leads to the following questions:
1. Why is
Martin Seine [EMAIL PROTECTED] wrote:
Tue Apr 16 18:06:18 2002 : Error: WARNING: Unresponsive child (id 9226) for=
request 68
Tue Apr 16 18:06:23 2002 : Error: Dropping duplicate authentication packet=
from client 1.2.3.4:1645 - ID: 60
Some more seconds later maximum number of childs
Hello,
I tried to install version 0.5 and got after a few seconds following
errors:
Tue Apr 16 18:05:42 2002 : Error: WARNING: Unresponsive child (id 2051) for request 57
Tue Apr 16 18:05:42 2002 : Error: WARNING: Unresponsive child (id 6151) for request 59
Tue Apr 16 18:05:47 2002 : Error
All,
I just upgraded from 0.4 to 0.5 and my radius service keeps crashing with
the following error Error: WARNING: Unresponsive child (id 13326) for
request 12. Before this problem started I was getting Info: The maximum
number of threads (250) are active, cannot spawn new thread to handle
the entire request list ---
WARNING: Unresponsive child (id 1883138) for request 1838
WARNING: Unresponsive child (id 1883138) for request 1838
WARNING: Unresponsive child (id 1885186) for request 1840
WARNING: Unresponsive child (id 1885186) for request 1840
WARNING: Unresponsive child (id 1886210
13 matches
Mail list logo
