2016-11-29 - question on GRASE freeradius temp file

Header Data

From: Gianluca Filippini <gi***4@gmail.com>
Message Hash: efa05dbe26d7e61065a47401622e2878cf0b49b291685571db2994ebe6f6921d
Message ID: <3153bc50-6244-4d92-a9a9-0e00725444e2@grasehotspot.org>
Reply To: N/A
UTC Datetime: 2016-11-29 12:24:29 UTC
Raw Date: Tue, 29 Nov 2016 11:24:29 -0800

Raw message 

Hi Tim,
in a previous post I was referring to poor performance on a old 
installation of grase (3.7)

the issue is presenting as a long delay from the moment a registered user 
asks for a website and the moment he gets the page.
the delay is huge ... up to minutes ... on a very powerful machine (4 cores 
3Ghz Xeon with 16G ram) and a very fast internet link (100Mbit/s fiber)
the average internet load is 90 users connected with a 20/30Mbit/s traffic.

so I focused my attention on the freeradius package and I found that the 
var/log/freeradius/radwtmp was getting huge after few days ... up to 600M+

my understanding is that this file is used by freeradius to detect MULTIPLE 
SESSION which indeed I do *not* allow in my GRASE user account group.

===
My theory is that every time a user does a request this file has to be 
parsed to prevent double sessions, adding a big delay to the user response,
so I deleted the file (it is a temp file) and I will monitor performance 
next .. but ..

is this some sort of known issue that has been addressed in v.3.8 ?

I see that multiple session can be adressed either by using mysql (raddact 
table) OR radwtmp file .. 
do you know which one we are using?

thanks

Thread