Hi, I am getting this error in my radius log, do you know why this is so and how to get this resolved? 'The maximum number of threads (32) are active, cannot spawn new thread to handle request' Also, do people know what is the maximum simultaneous incoming authentication calls that the radius process can handle? Or what ways can be adopted to deal with this? Thanks Ackbar No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.17.13/1212 - Release Date: 06/01/2008 22:55
Hi,
'The maximum number of threads (32) are active, cannot spawn new thread to handle request'
FreeRADIUS is getting many many requests but cannot handle them in real time - usually due to the authentication or accounting being too slow - you use SQL or AD for authentication? SQL for accounting?
Also, do people know what is the maximum simultaneous incoming authentication calls that the radius process can handle? Or what ways can be adopted to deal with this?
we have ours at over 128 without any local issues alan
Dear All, I have freeradius-1.1.7-1. it was installed on RHEL 3 SNMP net-snmp-5.0.9-2.30E.22 every thing was going OK i just installed RHEL 5 64-bit recompiled the freeradius on the new OS and reinstall the radius is working Ok i have SNMP version net-snmp-5.3.1-19.el5 but every time i wanted to snmpwalk from the radius i got that error " RADIUS-AUTH-SERVER-MIB::radiusMIB = No Such Object available on this agent at this OID " the command i execute is " snmpwalk -v2c -c testsnmp -m /etc/raddb/RADIUS-AUTH-SERVER-MIB.txt localhost radius " same command is working fine on the old machine. i searched for that on google but found nothing . any one can help ?? thanks Amr
On Thursday 10 January 2008 08:41:30 Amr el-Saeed wrote:
but every time i wanted to snmpwalk from the radius i got that error " RADIUS-AUTH-SERVER-MIB::radiusMIB = No Such Object available on this agent at this OID "
the command i execute is " snmpwalk -v2c -c testsnmp -m /etc/raddb/RADIUS-AUTH-SERVER-MIB.txt localhost radius " same command is working fine on the old machine.
i searched for that on google but found nothing .
any one can help ??
What does debug mode (-X) show? Are there any errors in your snmpd log file? Kevin Bonner
this is the log [smux_accept] accepted fd 12 from 127.0.0.1:57180 Jan 10 20:38:26 RADIUS-1-A snmpd[32488]: refused smux peer: oid SNMPv2-SMI::enterprises.3317.1.3.1, descr radiusd Jan 10 20:38:26 RADIUS-1-A snmpd[32488]: [smux_accept] accepted fd 12 from 127.0.0.1:57181 Jan 10 20:38:26 RADIUS-1-A snmpd[32488]: refused smux peer: oid SNMPv2-SMI::enterprises.3317.1.3.1, descr radiusd Jan 10 20:38:26 RADIUS-1-A snmpd[32488]: [smux_accept] accepted fd 12 from 127.0.0.1:57182 Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: refused smux peer: oid SNMPv2-SMI::enterprises.3317.1.3.1, descr radiusd Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: [smux_accept] accepted fd 12 from 127.0.0.1:57183 Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: refused smux peer: oid SNMPv2-SMI::enterprises.3317.1.3.1, descr radiusd Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: [smux_accept] accepted fd 12 from 127.0.0.1:57184 Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: refused smux peer: oid SNMPv2-SMI::enterprises.3317.1.3.1, descr radiusd Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: [smux_accept] accepted fd 12 from 127.0.0.1:57185 Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: refused smux peer: oid SNMPv2-SMI::enterprises.3317.1.3.1, descr radiusd Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: [smux_accept] accepted fd 12 from 127.0.0.1:57186 Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: refused smux peer: oid SNMPv2-SMI::enterprises.3317.1.3.1, descr radiusd Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: [smux_accept] accepted fd 12 from 127.0.0.1:57187 Jan 10 20:38:27 RADIUS-1-A snmpd[32488]: refused smux peer: oid SNMPv2-SMI::enterprises.3317.1.3.1, descr radiusd this is the debug mode SMUX read start SMUX connection closed: 66 SMUX connect try 1 SMUX open oid: 1.3.6.1.4.1.3317.1.3.1 SMUX open progname: radiusd SMUX open password: yallasnmp SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 SMUX register priority: -1 SMUX register operation: 1 SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 SMUX register priority: -1 SMUX register operation: 1 Waking up in 14 seconds... SMUX read start SMUX read len: 3 SMUX message received type: 0 rest len: 1 Unknown type: 0 Waking up in 14 seconds... SMUX read start SMUX connection closed: 66 SMUX connect try 1 SMUX open oid: 1.3.6.1.4.1.3317.1.3.1 SMUX open progname: radiusd SMUX open password: yallasnmp SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 SMUX register priority: -1 SMUX register operation: 1 SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 SMUX register priority: -1 SMUX register operation: 1 Waking up in 14 seconds... Kevin Bonner wrote:
On Thursday 10 January 2008 08:41:30 Amr el-Saeed wrote:
but every time i wanted to snmpwalk from the radius i got that error " RADIUS-AUTH-SERVER-MIB::radiusMIB = No Such Object available on this agent at this OID "
the command i execute is " snmpwalk -v2c -c testsnmp -m /etc/raddb/RADIUS-AUTH-SERVER-MIB.txt localhost radius " same command is working fine on the old machine.
i searched for that on google but found nothing .
any one can help ??
What does debug mode (-X) show? Are there any errors in your snmpd log file?
Kevin Bonner
------------------------------------------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
hi, known SNMP issues with 64bit and that version of SNMP. you will need to follow the debug instructions to help debug alan
hi alan, i searched the freeradius.org for the debug instructions, but i found nothing. what do you mean exactly by debug instructions i already have this in the radius debug mode SMUX read start SMUX connection closed: 66 SMUX connect try 1 SMUX open oid: 1.3.6.1.4.1.3317.1.3.1 SMUX open progname: radiusd SMUX open password: yallasnmp SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 SMUX register priority: -1 SMUX register operation: 1 SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 SMUX register priority: -1 SMUX register operation: 1 Waking up in 14 seconds... SMUX read start SMUX read len: 3 SMUX message received type: 0 rest len: 1 Unknown type: 0 Waking up in 14 seconds... SMUX read start SMUX connection closed: 66 SMUX connect try 1 SMUX open oid: 1.3.6.1.4.1.3317.1.3.1 SMUX open progname: radiusd SMUX open password: yallasnmp SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 SMUX register priority: -1 SMUX register operation: 1 SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 SMUX register priority: -1 SMUX register operation: 1 Waking up in 14 seconds... thanks amr A.L.M.Buxey@lboro.ac.uk wrote:
hi,
known SNMP issues with 64bit and that version of SNMP. you will need to follow the debug instructions to help debug
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
hi alan,
i searched the freeradius.org for the debug instructions, but i found nothing. what do you mean exactly by debug instructions i already have this in the radius debug mode
read doc/bugs in the distribution tar file. i can send you a copy if your archive doesnt contain it. beware that you will need an OS kernel that has all the debugging flags enabled (most default distro kernels are compiled in such a way) I have reported this bug to bugs.freeradius.org with the debug output that my system was able to generate alan
Hi Alan, Sorry for the large delay . i followed the bugs file. i recompiled the freeradius with --enable-developer actually i made RPM file with ( rpmbuild -ta freeradius-1.1.7.tar.gz ) i installed the RPM file ulimit -c unlimited gdb radiusd (gdb) set logging file gdb-radiusd.log (gdb) set logging on Copying output to gdb-radiusd.log. run and that what i got Starting program: /usr/sbin/radiusd (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912546236704 (LWP 28074)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Mon Jan 21 14:47:10 2008 : Info: Starting - reading configuration files ... (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program exited normally. (gdb) did i do some-thing wrong ?? A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
hi alan,
i searched the freeradius.org for the debug instructions, but i found nothing. what do you mean exactly by debug instructions i already have this in the radius debug mode
read doc/bugs in the distribution tar file. i can send you a copy if your archive doesnt contain it. beware that you will need an OS kernel that has all the debugging flags enabled (most default distro kernels are compiled in such a way)
I have reported this bug to bugs.freeradius.org with the debug output that my system was able to generate
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
i followed the bugs file. i recompiled the freeradius with --enable-developer actually i made RPM file with ( rpmbuild -ta freeradius-1.1.7.tar.gz )
are you SURE That this worked fine - as if you used the standard SPEC then you wouldnt enable the developer stuff.
(no debugging symbols found)
you also need to ensure your kernel is built with debugging support alan
Hi Alan, yes, i'm sure i added the option in the SPEC file and then build the RPM and about the second issue , i didn't have a debugging kernel but i got one and install it and boot with it and got the same output !! and ideas ?? thanks for help (gdb) set logging file gdb-radiusd.log (gdb) set logging on Copying output to gdb-radiusd.log. (gdb) run Starting program: /usr/sbin/radiusd (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912546236704 (LWP 5584)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Wed Jan 23 15:46:53 2008 : Info: Starting - reading configuration files ... (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program exited normally. (gdb) A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
i followed the bugs file. i recompiled the freeradius with --enable-developer actually i made RPM file with ( rpmbuild -ta freeradius-1.1.7.tar.gz )
are you SURE That this worked fine - as if you used the standard SPEC then you wouldnt enable the developer stuff.
(no debugging symbols found)
you also need to ensure your kernel is built with debugging support
alan
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
i have OS RHEL5 Amr el-Saeed wrote:
Hi Alan,
yes, i'm sure i added the option in the SPEC file and then build the RPM
and about the second issue , i didn't have a debugging kernel but i got one and install it and boot with it and got the same output !!
and ideas ??
thanks for help
(gdb) set logging file gdb-radiusd.log (gdb) set logging on Copying output to gdb-radiusd.log. (gdb) run Starting program: /usr/sbin/radiusd (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912546236704 (LWP 5584)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Wed Jan 23 15:46:53 2008 : Info: Starting - reading configuration files ... (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found)
Program exited normally. (gdb)
A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
i followed the bugs file. i recompiled the freeradius with --enable-developer actually i made RPM file with ( rpmbuild -ta freeradius-1.1.7.tar.gz )
are you SURE That this worked fine - as if you used the standard SPEC then you wouldnt enable the developer stuff.
(no debugging symbols found)
you also need to ensure your kernel is built with debugging support
alan
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
i have OS RHEL5
it looks like it didnt build with the required debug parts - once again, as you are using the SPEC for your distro they could have other things that mess it up - I can only help if you build from the source and leave package management stuff alone. alan
Dear Alan, i build from the source file that i downloaded from freeradius.org i suspected the 64-bit i made several trials , and here is the result freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL3 , 32-bit working freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL5 , 32-bit working freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL5 , 64-bit NOT working freeradius-1.1.7 , snmp-5.3.1-19.el5 , RHEL5 , 32-bit NOT working freeradius-1.1.7 , snmp-5.3.1-19.el5 , RHEL5 , 64-bit NOT working any comments ?? A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
i have OS RHEL5
it looks like it didnt build with the required debug parts - once again, as you are using the SPEC for your distro they could have other things that mess it up - I can only help if you build from the source and leave package management stuff alone.
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi, any suggestions about what to do to make snmp work on 64-bit?? Amr el-Saeed wrote:
Dear Alan,
i build from the source file that i downloaded from freeradius.org
i suspected the 64-bit
i made several trials , and here is the result
freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL3 , 32-bit working freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL5 , 32-bit working freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL5 , 64-bit NOT working freeradius-1.1.7 , snmp-5.3.1-19.el5 , RHEL5 , 32-bit NOT working freeradius-1.1.7 , snmp-5.3.1-19.el5 , RHEL5 , 64-bit NOT working
any comments ??
Hi,
i have OS RHEL5
it looks like it didnt build with the required debug parts - once again, as you are using the SPEC for your distro they could have other things that mess it up - I can only help if you build from the source and leave package management stuff alone.
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
A.L.M.Buxey@lboro.ac.uk wrote: - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Dear Alan,
i build from the source file that i downloaded from freeradius.org
i suspected the 64-bit
i made several trials , and here is the result
freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL3 , 32-bit working freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL5 , 32-bit working freeradius-1.1.7 , snmp-5.0.9-2.30E.20 , RHEL5 , 64-bit NOT working freeradius-1.1.7 , snmp-5.3.1-19.el5 , RHEL5 , 32-bit NOT working freeradius-1.1.7 , snmp-5.3.1-19.el5 , RHEL5 , 64-bit NOT working
any comments ??
Hi,
i have OS RHEL5
it looks like it didnt build with the required debug parts - once again, as you are using the SPEC for your distro they could have other things that mess it up - I can only help if you build from the source and leave package management stuff alone.
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
A.L.M.Buxey@lboro.ac.uk wrote: - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hello, I am also curious about the answer on this question ! Are there any plans to implement AgentX protocol into freeradius project? Alan? Kind regards, E:S -----Original Message----- From: freeradius-users-bounces+edvin.seferovic=kolp.at@lists.freeradius.org [mailto:freeradius-users-bounces+edvin.seferovic=kolp.at@lists.freeradius.or g] On Behalf Of Amr el-Saeed Sent: Dienstag, 05. Februar 2008 09:05 To: FreeRadius users mailing list Subject: Re: SNMP error Hi, any suggestions about what to do to make snmp work on 64-bit?? Amr el-Saeed wrote: - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Amr el-Saeed wrote:
i have OS RHEL5
yes, i'm sure i added the option in the SPEC file and then build the RPM
and about the second issue , i didn't have a debugging kernel but i got one and install it and boot with it and got the same output !!
made RPM file with ( rpmbuild -ta freeradius-1.1.7.tar.gz )
rpmbuild creates a separate package with the debugging information. You need to install the debuginfo rpm which was created in addition to the other rpms it created to get the debugging symbols, etc. I doubt you'll need a kernel with debugging. -- John Dennis <jdennis@redhat.com>
participants (7)
-
A.L.M.Buxey＠lboro.ac.uk -
Ackbar Joolia -
Alan DeKok -
Amr el-Saeed -
Edvin Seferovic -
John Dennis -
Kevin Bonner