memory leaks with rlm_perl? (FreeRADIUS bug #221)
Hello, I wonder if you were able to resolve this bug? ref http://bugs.freeradius.org/show_bug.cgi?id=221 The reason I ask is that I've just experienced a serious memory leak after upgrading from 1.0.1 to 1.0.5, and we do use rlm_perl so that is one module to suspect. It seems that a colleague of mine has had the same experience previously too, trying to upgrade to 1.0.4. We don't really _know_ that rlm_perl is the cause, though... I will attempt to track the bug down further and provide a test configuration that will demonstrate the problem. Just wondered if you had some ideas we might test first. FWIW, we've been running 1.0.5 on a test server for a couple of months without trouble at all. The problems first showed up when upgrading the heavily loaded production servers. Our configuration was not changed at all on upgrade. I will eventually provide it to aid recreating the bug, but I need som time first to remove all private data from it. Sorry about that. Feel free to ignore me until I've been able to do this work. Just wanted to give an early warning in case someone has the magic solution at hand. Bjørn
"Alan DeKok" <aland@ox.org> writes:
=?iso-8859-1?Q?Bj=F8rn_Mork?= <bjorn@mork.no> wrote:
We don't really _know_ that rlm_perl is the cause, though...
Try grabbing revision 1.19 of rlm_perl from CVS.
Thanks! Looks very good so far. I also got a tip from Boyan Jordanov on how to configure a fixed size thread pool for rlm_perl, which also seemed to fix the problem. I really appreciate that the FreeRADIUS developers actually take their time to do end user support on this list. I am impressed by the work you all do. Getting two(!) working solutions to a problem in a couple of hours during the weekend, is a level of support that I think you can't buy from any commercial company at any price. It makes me wish that I had something to give back. At least I'll have an example for all the bosses that express their concern about "unsupported" open source solutions.. Thanks again. Bjørn
I really appreciate that the FreeRADIUS developers actually take their time to do end user support on this list. I am impressed by the work you all do. Getting two(!) working solutions to a problem in a couple of hours during the weekend, is a level of support that I think you can't buy from any commercial company at any price. It makes me wish that I had something to give back. At least I'll have an example for all the bosses that express their concern about "unsupported" open source solutions..
Thanks again.
I agree with you 100% on this. Our company pays extra for so-called "support" on many of the commercial products we use. However, I've found that the community that supports freeradius on this mailling list is much more valuable than any of our paid support on commercial software. The support here on the list comes from people that actually USE the product in a PRODUCTION network. This is something you can't always get from a commercial product. You definately can give back by documenting anything you think might help and sending it to the list. Or perhaps you can stay on the list and see if you can help anyone with similar issues to what you've experienced. I'm in the same boat as you, and trying to give back by occassionally responding to threads here and sending in some documentation whenever I get the time to write some up. -Dusty Doris
participants (3)
-
Alan DeKok -
Bjørn Mork -
Dusty Doris