No cleanup for abandoned EAP requests in radiusd
Kunal Solanki
tokunal_80 at rediffmail.com
Wed Jun 23 11:25:56 CEST 2010
Hi All,
I have been using freeradius version 2.1.4 and when I upgraded to 2.1.7 I am facing issues of high memory usage by radiusd. In 2.1.4 also the memory usage was quite high under high load but it used to come down after some time when abandoned requests are cleaned up. The cleanup trigger is not timer based in freeradius and is part of ongoing requests. In 2.1.7 version somehow this cleanup doesn't happen effectively and looks like for the same EAP requests a lot of dangling handlers are created which are not getting cleaned. I tried to cleanup old handlers in src/modules/rlm_eap/mem.c but that causes other side-affects of requests being present and no matching session state variable found for that.
I believe in src/main/event.c we should have some sought of cleanup for the old requests itself.
Please suggest,
Thanks,
Kunal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20100623/0558c881/attachment.html>
More information about the Freeradius-Devel
mailing list