FreeRADIUS exiting with Signal 11 on FreeBSD
Danial
dol at ft.fo
Mon Dec 20 13:56:13 CET 2010
Tim Sylvester wrote:
>
> You need to run radiusd in single threaded mode. The server forks a couple
> processes to run the server as a daemon and then exits normally. If you
> looked at the process table (ps -ef), you should see a copy of freeradius
> running on your system.
>
> In gdb, set the arguments for radiusd using set args
>
> gdb> set args -f
> gdb> run
>
I did what you suggested and have captured another exit:
# gdb radiusd
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
(gdb) set logging file gdb-radiusd.log
(gdb) set logging on
Copying output to gdb-radiusd.log.
(gdb) set args -f
(gdb) run
Starting program: /usr/local/sbin/radiusd -f
[New LWP 100056]
[New Thread 28401140 (LWP 100056)]
[New Thread 28567ac0 (LWP 100051)]
[New Thread 28567980 (LWP 100068)]
[New Thread 28567840 (LWP 100069)]
[New Thread 28567700 (LWP 100070)]
[New Thread 285675c0 (LWP 100102)]
Program received signal SIGABRT, Aborted.
[Switching to Thread 28567ac0 (LWP 100051)]
0x2831866b in thr_kill () from /lib/libc.so.7
(gdb)
What do you make of this?
--
Danial
--
View this message in context: http://freeradius.1045715.n5.nabble.com/FreeRADIUS-exiting-with-Signal-11-on-FreeBSD-tp3293576p3311917.html
Sent from the FreeRadius - User mailing list archive at Nabble.com.
More information about the Freeradius-Users
mailing list