Radius server crash due to 35# bug
aland at deployingradius.com
Wed Apr 7 13:52:28 CEST 2010
Liu Linyong wrote:
> The conclusion:
> The 35# bug can recur rather easily.
Hmm... I've run the server at 40K packets/s for *days*, and have been
unable to reproduce it.
> We found FreeRadius server crash sometimes with load.
> Then use gdb to run 'radiusd', and do load test with LoadRunner, which sending thousands of requests per second.
How many requests in parallel? How many threads is the server using?
> FreeRadius will cost little mem(16M) and cpu(1.6%).
> After an hour or so, the server will crash. These can be repeated easily. gdb show the position:
It looks like a race condition, where data is accessed after it's been
freed. However, tracking it down is hard.
More information about the Freeradius-Devel