Re: [RADIATOR] more memory leakage?

On 27.9.2016 18.54, Fredrik Pettai wrote: > Sorry, then I wrote authentication handled, I meant by proxying requests… > > These Radiators are just doing proxying inbetween all our IdP’s in .se > (they are the FLRS's for .SE), and the eduroam ETLR’s (root) servers… Earlier you mentioned you

Re: [RADIATOR] more memory leakage?

ubject: Re: [RADIATOR] more memory leakage? > On 27 Sep 2016, at 11:32, Heikki Vatiainen <h...@open.com.au> wrote: > > On 26.9.2016 16.40, Fredrik Pettai wrote: > >> (A rough guestimate of the number of radius authentications handled >> by these servers is ~500

Re: [RADIATOR] more memory leakage?

> On 27 Sep 2016, at 11:32, Heikki Vatiainen wrote: > > On 26.9.2016 16.40, Fredrik Pettai wrote: > >> (A rough guestimate of the number of radius authentications handled >> by these servers is ~500.000 Accepts/Rejects per day, RADSEC is >> enabled/running too...) > > If you

Re: [RADIATOR] more memory leakage?

On 26.9.2016 16.40, Fredrik Pettai wrote: > (A rough guestimate of the number of radius authentications handled > by these servers is ~500.000 Accepts/Rejects per day, RADSEC is > enabled/running too...) If you are using EAP and have not disabled session resumption, can you try setting

Re: [RADIATOR] more memory leakage?

On 26.09.2016 16:40, Fredrik Pettai wrote: > I saw that 4.17 was released, and it was plugging at least one memory leak > according to the Release notes. > So I’ve upgraded our systems now, but it still looks like Radiator is > continuing to consume memory at a very fast phase... Can you reply

[RADIATOR] more memory leakage?

Hi, Since we upgraded OS + Radiator to version 4.16 + patches, we’ve noted that Radiator seemed to leak memory. From having a very small memory footprint, it now consumes 500MB+ of Ram in just a day or two, and keeps on growing... I saw that 4.17 was released, and it was plugging at least one