radiusd stop responding. deadlock?
Alan DeKok
aland at deployingradius.com
Fri Jun 22 07:54:23 CEST 2007
blue_11j at yahoo.co.jp wrote:
> We using freeradius 1.1.0 for PEAP authentication,
> and it is working well almost.
Use 1.1.6. It has a NUMBER of bugs fixed over 1.1.0.
...
> (gdb) attach 10127
> Attaching to program: /usr/dot1x/sbin/radiusd, process 10127
> Symbols already loaded for /lib/libcrypt.so.1
> ....(snip)...
> 0x401998cc in pthread_mutex_trylock () from /lib/libpthread.so.0
> (gdb) whrere
> #0 0x401998cc in pthread_mutex_trylock () from /lib/libpthread.so.0
If the code is blocking in the libc malloc() implementation, there
isn't much that FreeRADIUS can do to fix that.
Try upgrading to 1.1.6, and see if that fixes it. I don't know...
Alan DeKok.
More information about the Freeradius-Users
mailing list