Version 1.1.1 stops responding
Alan DeKok
aland at ox.org
Tue Mar 28 00:37:57 CEST 2006
"King, Michael" <MKing at bridgew.edu> wrote:
> How would I create those traces? (I'm looking for a suggested command
> line, since I don't normally use those programs)
I'd suggest gdb, and do it in a testing environment if at all
possible, to avoid hitting your main server. Also, you *must* have
symbols in the binary, meaning that the "make install" process can't
strip the binaries. You may need to edit the Makefiles for this...
$ gdb radiusd
(gdb) set args -d ... <<<- normal radiusd args
(gdb) run
And when it stops responding, hit CTRL-C, and see what's up:
(gdb) info threads
That *may* be enough. What will also help (if you have symbols) is:
(gdb) thread 1
(gdb) bt
(gdb) thread 2
(gdb) bt
(gdb) thread 3
(gdb) bt
...
For each of the threads it talks about in "info threads".
Alan DeKok.
More information about the Freeradius-Users
mailing list