Norbert Wegener wrote: > In a cvs version of pre2, which is newer than pre2, on one machine, > after some time of inactivity, freeradius does not seem to answer at > all- sometimes, not > reliable reproducable.
When did you take the CVS snapshot? Did -pre2 NOT have this behavior? ... > with a few dozens lines deleted. It looks like the threads are blocked on reading a descriptor, OR on a mutex. Which mutex they're blocked on is anyone's guess. > strace's output stops here, also when radius request come in. They are > not answered. > Any idea, what's going wrong here or how to track that down? > I already tried > nohup gdb -x gdbargs /sbin/radiusd & > with gdbargs containing: > run -AX > bt > > but was unable to reproduce that situation in this context. You can use gdb to attach to a running process, and then type "bt" to see where it's blocked. > Running radiusd under gdb's control seemed to solve that problem, maybe > that's not the final solution. Sounds like it's a signal/mutex issue... Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
