Phil Mayers <p.mayers@imperial.ac.uk> wrote:
Ah ha - presumably that was why my 2.1.12 install ballooned it's RAM; it was nothing to do with 2.1.12, but the fact I'd enabled session resumption.
I guess everyone out there is restarting their servers nightly!
We have session resumption enabled (lifetime 24 and max_entries 8192) and we do not have any problems: ---- ac56@iodine:~$ stat /proc/$(pgrep freeradius) File: `/proc/6397' Size: 0 Blocks: 0 IO Block: 1024 directory Device: 3h/3d Inode: 65547285 Links: 7 Access: (0555/dr-xr-xr-x) Uid: ( 104/ freerad) Gid: ( 107/ freerad) Access: 2011-10-14 10:11:20.817205244 +0100 Modify: 2011-10-14 10:11:20.817205244 +0100 Change: 2011-10-14 10:11:20.817205244 +0100 TOP: 6397 freerad 20 0 214m 68m 3752 S 0.8 13.6 231:24.81 freeradius ---- ac56@chlorine:~$ stat /proc/$(pgrep freeradius) File: `/proc/28449' Size: 0 Blocks: 0 IO Block: 1024 directory Device: 3h/3d Inode: 42368844 Links: 7 Access: (0555/dr-xr-xr-x) Uid: ( 103/ freerad) Gid: ( 104/ freerad) Access: 2011-10-14 10:11:45.126296091 +0100 Modify: 2011-10-14 10:11:45.126296091 +0100 Change: 2011-10-14 10:11:45.126296091 +0100 28449 freerad 20 0 94276 26m 3796 S 3.1 5.3 69:32.58 freeradius ---- Only restarted on the 14th as I was adding a new configuration tweaking (that nice rlm_replicate bits for eduroam accounting proxying) but our setup can run for weeks with no memory leak woes. Ages ago we did have a rlm_detail related memory leak but I think that was fixed in 2.1.11. The extra high memory usage on ours is probably related to the rlm_perl instance[1]. Cheers [1] http://www.mail-archive.com/freeradius-users@lists.freeradius.org/msg65781.h... -- Alexander Clouter .sigmonster says: BOFH excuse #58: high pressure system failure