(RADIATOR) Re: duplicate entries for accounting ( Radiator radius)

[Hugh Irvine]

Hello Eapen -

On Fri, 11 Jan 2002 05:06, Eapen Joseph wrote:
> Dear Hugh,
> I get a lot of Duplicate entries for accounting. A part of the log file
> for the case is given below.
>
> Thu Jan 10 18:16:09 2002: ERR: do failed for 'insert into
> Q8ACCOUNTINGTABLE6
>                 (USERNAME, CALLDATE1, ACCTSTATUSTYPE, ACCTDELAYTIME,
> ACCTINPUTOCTETS, ACCTOUTPUTOCTETS, ACCTSESSIONID, ACCTSESSIONTI
> ME, ACCTTERMINATECAUSE, NASIDENTIFIER, NASPORT, CLIENTIPADDRESS)
>                 values
>                 ('64453215', '2002 01 10 18:16:03', 2, 6, 561296,
> 3094424, '020110.172641.022183', 2767, 'User-Request', '195.39.142
> .22', 108, '62.150.38.14')': Duplicate entry '64453215-2002-01-10
> 18:16:03' for key 1
> Thu Jan 10 18:16:09 2002: ERR: do failed for 'insert into
> Q8ACCOUNTINGTABLE6
>                 (USERNAME, CALLDATE1, ACCTSTATUSTYPE, ACCTDELAYTIME,
> ACCTINPUTOCTETS, ACCTOUTPUTOCTETS, ACCTSESSIONID, ACCTSESSIONTI
> ME, ACCTTERMINATECAUSE, NASIDENTIFIER, NASPORT, CLIENTIPADDRESS)
>                 values
>                 ('64453215', '2002 01 10 18:16:03', 2, 6, 561296,
> 3094424, '020110.172641.022183', 2767, 'User-Request', '195.39.142
> .22', 108, '62.150.38.14')': Duplicate entry '64453215-2002-01-10
> 18:16:03' for key 1
> Thu Jan 10 18:21:37 2002: ERR: do failed for 'insert into
> Q8ACCOUNTINGTABLE6
>
> The Dupinterval in the radiator configuraion file is set to 3.
>
> On the access-server the configuration is set in such a way so as to
> send 4(retry_count) accounting packets at a retry_interval of 6 seconds.
>
> we also tried changing the Dupinterval to a value greater than 6 so
> that the second accounting packet send by the access-server is
> considered as a Duplicate by the radiator.
>
> Is it because the access-server is not receiving an ack from the
> radiatior for the accounting packet?
>

You are correct - if the NAS does not receive an accounting response for an 
accounting packet, it will resend the packet according to the timeout and 
retries as configured on the NAS. There are a couple of other possible causes 
such as Radiator not sending an accounting response or the NAS having a 
software bug.

The best way to check is first of all to look at a trace 4 debug from 
Radiator to verify that the accounting response is being sent, and if it is 
then do a debug on the NAS to see what is happening there. If Radiator is 
sending the accounting response and the NAS is not receiving it, it may be 
because of saturated links, routing problems or packet filters dropping the 
packets.

hth

Hugh

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.