Hello Sergey,
We use a SQL server (separated machine)
the config file looks like this :
# For detailed description, run:
# info Radius config
option {
radiusd-user radius;
max-requests 1024;
resolve no;
};
logging {
prefix-hook "default_log_prefix";
channel default {
file "radius.log";
print-category yes;
print-level yes;
};
category auth {
print-auth yes;
print-failed-pass yes;
channel default;
};
category info {
channel default;
};
category debug {
channel default;
#level radiusd=1,files,sql=99,auth,input;
};
category * {
channel default;
};
};
auth {
listen
193.109.184.73:1812,
193.109.184.74:1812,
192.168.3.2:1812;
max-requests 127;
request-cleanup-delay 2;
detail yes;
strip-names yes;
checkrad-assume-logged yes;
};
acct {
listen
193.109.184.73:1813,
193.109.184.74:1813,
192.168.3.2:1813;
max-requests 127;
request-cleanup-delay 2;
};
rewrite {
load "
checknas.rw";
load "
log-hook.rw";
};
# snmp {
# listen no;
# };
our radius.log file is filled with
Jan 05 11:40:33 Auth.notice: (Access-Request 172.28.3.158 27 "dsl28543" CLID=*BAS-ANTWERPEN*19/0*247*487): Dropping packet: Maximum number of children active
Jan 05 11:40:33 Auth.notice: (Access-Request 172.28.192.233 11 "dsl35220" CLID=*MSR02MAR1*13/1*213*84): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Acct.notice: (Accounting-Request 172.28.3.158 3 "dsl29126" CLID=*BAS-ANTWERPEN*21/1*242*304): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Acct.notice: (Accounting-Request 172.28.3.190 2 "dsl37161" CLID=*BAS-LEUVEN*21/1*245*386): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Acct.notice: (Accounting-Request 172.28.3.10 2 "dsl31163" CLID=*BAS-ROGIER*27/1*241*1846): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Auth.notice: (Access-Request 172.28.3.10 96 "dsl31163" CLID=*BAS-ROGIER*27/1*241*1846): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Acct.notice: (Accounting-Request 172.28.3.182 8 "dsl43156" CLID=*BAS-HASSELT*23/0*210*372): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Acct.notice: (Accounting-Request 172.28.3.158 5 "dsl31350" CLID=*BAS-ANTWERPEN*27/1*29*377): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Acct.notice: (Accounting-Request 172.28.3.158 9 "dsl43067" CLID=*BAS-ANTWERPEN*19/0*246*421): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Acct.notice: (Accounting-Request 172.28.3.198 40 "dsl30089" CLID=*BAS-LIEGE*23/1*217*128): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Acct.notice: (Accounting-Request 172.28.18.98 3 "dsl43597" CLID=*BAS-BERCHEM*23/1*204*898): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Auth.notice: (Access-Request 172.28.192.234 30 "dsl20464" CLID=*MSR02STR1*14/1*248*99): Dropping packet: Maximum number of children active
Jan 05 11:40:34 Auth.notice: (Access-Request 172.28.192.238 26 "dsl45173" CLID=*MSR11HAS1*13/1*225*310): Dropping packet: Maximum number of children active
Jan 05 11:40:35 Auth.notice: (Access-Request 172.28.192.240 2 "dsl18008" CLID=*MSR15MES1*11/1*229*1305): Dropping packet: Maximum number of children active
Jan 05 11:40:35 Acct.notice: (Accounting-Request 172.28.3.10 8 "dsl31163" CLID=*BAS-ROGIER*27/1*241*1846): Dropping packet: Maximum number of children active
on a previous machine running on CentOS with kernel 2.4.25 running with gnu radius 1.2 has never got the problem.
This machine is a CentOS 5.2 with gnu radius 1.4 or 1.5 (tried both)
Hope you can help me?
2009/1/3 Sergey Poznyakoff
<address@hidden>
Bert Colemont <address@hidden> ha escrit:
> Now frequently the machine gets a load of 20, of radiusd, and in the
> log the message : Dropping packet : Maximum number of children active
There is not enough information to correctly diagnose your problem:
1. What is your configuration? In particular, files radd/config, users.
hints, huntgroups. If you use SQL, then raddb/sqlserver also.
2. What command options are used when starting daemon?
2. What do you get in your logs?
Regards,
Sergey