Hi,

...

well, due to the way the log files and logrotate clash, our servers have a daily restart right now.... so this masks any such issue so cant say :-|

I probably asked this already but why not syslog-ng and yyyymmdd.log as an output?

because the system should be as vanilla as possible and the behaviour of FreeRADIUS changed (due to some random request). it used to quite happily start writing to a new logfile after logrotate had done its business. and actually, a daily blip is quite nice for avoiding nasty longterm memory leaks ;-) its not good really....the EAP cache is lost for a start (as the daemon doesnt/cant save that cache upon stop/start) alan

On 13/10/11 13:31, Alan DeKok wrote:

Phil Mayers wrote:

...

All,

We recently upgraded to 2.1.12 and I have at the same time enabled SSL fast session resumption; in the last 6 days, FreeRADIUS on the server that is currently handling most of our auth has consumed 27% of the RAM.

Is anyone else running fast session resumption and seeing these symptoms, or not?

No idea... maybe try changing "max_entries", or using valgrind?

If you have a Mac, xcode has all kinds of wonderful tools for tracking memory allocations in running processes.

valgrind is, so far, reporting nothing useful. I am wondering if it's actually unrelated to fast session resumption; the CPU use has jumped alarmingly too, and doesn't drop back when I disable session resumption. I might try downgrading and see if it goes away.

On 13/10/11 14:49, Alan DeKok wrote:

Phil Mayers wrote:

...

I am wondering if it's actually unrelated to fast session resumption; the CPU use has jumped alarmingly too, and doesn't drop back when I disable session resumption.

Hmm... I don't recall any new "use tons of CPU" code in 2.1.12.

Indeed - and other radius processes on that same server are working fine. I'll try to troubleshoot some more, but just wanted to see if anyone had any comparable experiences.