Please refer to the following post. =========================
Author: Alan DeKok Date: 2010-04-07 19:52 +800 To: FreeRadius developers mailing list Subject: Re: Radius server crash due to 35# bug
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? ====> 4K requests/sec. start_servers = 5 and max_servers = 32. But totally 9 threads were created.(That is: 3 more threads were created after initializing)
Oh, I've set max_requests = 102400 in radiusd.conf.
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.
Alan DeKok.
================================= Liu Linyong 2010-04-08