On Tue 29 Aug 2006 15:52, Santiago Balaguer García wrote:

Hi people,

I use freeradius 1.1.0 in a debian servers for several years. Now I use my radius server more than before. So in my DB it appears some strange duplicate registers which have the same inforrmation.

I show a snapshoot with an account where the problem happens: ------------------------------------ radacctid|acctsessionid|acctuniqueid|username|realm|nasipaddress|nasportid| nasporttype|acctstarttime|acctstoptime|acctsessiontime|acctauthentic|connect info_start|connectinfo_stop|acctinputoctets|acctoutputoctets|calledstationid |callingstationid|acctterminatecause|servicetype|framedprotocol|framedipaddr ess|acctstartdelay|acctstopdelay 153270|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 14:40:59.614916+02|2006-07-26 17:20:52.812241+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129|0|0 153395|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 15:03:29.945729+02|2006-07-26 17:20:52.945729+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129||16 153392|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 15:03:29.902309+02|2006-07-26 17:20:52.902309+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129||4 153393|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 15:03:29.929558+02|2006-07-26 17:20:52.929558+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129||8 153394|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 15:03:29.966051+02|2006-07-26 17:20:52.966051+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129||12 153396|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 15:03:29.983671+02|2006-07-26 17:20:52.983671+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129||20 153397|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 15:03:30.019645+02|2006-07-26 17:20:53.019645+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129||24 153398|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 15:03:30.047495+02|2006-07-26 17:20:53.047495+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129||28 153401|A2000001|9c4661a9f1471d42|aabo6098||172.19.242.50|0|Async|2006-07-26 15:03:29.204327+02|2006-07-26 17:20:52.204327+02|8243||||264229589|18168071|00-50-E8-02-42-FB|00-13-02-1D -12-58|Session-Timeout|||10.5.0.129||88 --------------------------------------------- I attach this info in a file <<registro.csv>>

As you can realize the last integer after the IP is acctstopdely. this values are 0, 4, 8, 12, 16, 20, 24, 28, 88. It is not usual this atribute was upper than 1. My request timeout is 4 secs. Well, this situation is very important because I have a ttriger to decrease the credit of this account. Moreover, the time which this account spent is NOT real.

What I don't know if the problem is in my NAS or there is a mistake in my freeradius configuration. Any sugestion??

It appears your database is not keeping up with the load, so when the NAS doesn't receive an answer in time it resends the request. Alternatively it could be caused by a network problem between radius and the NAS. Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc