Hello Brian -
Could you please send me a trace 4 debug from Radiator showing the
packet dumps when this happens?
I think you are right - there are two values in the same request.
Toomas probably has the right idea - a hook to pre-process the
attributes prior to insertion.
regards
Hugh
On Monday, Dec 9, 2002, at 19:09 Australia/Melbourne, Brian Morris
wrote:
Oops.. This didn't work quite right..
I added the following line to my radiator cfg file :
AcctColumnDef ACCTTERMINATECAUSE,Acct-Terminate-Cause
AcctColumnDef ACCTTERMINATECAUSE,Ascend-Disconnect-Cause
AcctColumnDef ACCTTERMINATECAUSE,LE-Terminate-Detail
Started up and got the following error...
Mon Dec 9 18:56:59 2002: ERR: do failed for 'insert into ACCOUNTING
(USERNAME, TIMESTAMP, ACCTSTATUSTYPE, ACCTDELAYTIME, ACCTINPUTOCTETS,
ACCTOUTPUTOCTETS, ACCTSESSIONID, ACCTSESSIONTIME, ACCTTERMINATECAUSE,
ACCTTERMINATECAUSE, NASIDENTIFIER, NASPORT, FRAMEDIPADDRESS,
CONNECTINFO)
values
('', 1039420619, 'Stop', 0, 8024, 160863, '4A00DCC7', 219,
'User-Request', 'User Request - PPP Term Req', '203.xx.xx.xx', '17',
'203.xx.xx.xx', '42666 LAPM/V42BIS')':
[Microsoft][ODBC SQL Server Driver][SQL Server]Column name
'ACCTTERMINATECAUSE' appears more than once in the result column list.
(SQL-37000)
[Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not
be
prepared. (SQL-37000)(DBD: st_prepare/SQLPrepare err=-1)
It appears that if Radiator receives two or more of the
ACCTTERMINATECAUSE
attributes in a stop record it tries to insert it twice (or more) in
the
same insert statement.
Is there a work around for this? Ideally to get it to concatenate
them all
into a single ACCTTERMINATECAUSE value. Perhaps something like the
timestamp / formatted date parameters
Thanks in advance..
Brian.
- Original Message -
From: Hugh Irvine [EMAIL PROTECTED]
To: Brian Morris [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 6:49 PM
Subject: Re: (RADIATOR) Multiple Items in the same AcctColumnDef
Hello Brian -
Yes this is possible, simply specify the AcctColumnDef twice.
Ie:
.
AcctColumnDef TERMINATECAUSE, Ascend-Disconnect-Cause
AcctColumnDef TERMINATECAUSE, Acct-Terminate-Cause
.
regards
Hugh
On Monday, Dec 9, 2002, at 18:38 Australia/Melbourne, Brian Morris
wrote:
Hi All,
We receive session info from a few different NAS's but I would like
to
store
all the connection specific information in a single table element.
EG: I
would like to store the Ascend-Disconnect-Cause as well as the
standard
Account-Terminate-Cause into the same table column.
Is this possible to do? If so, what is the syntax for the
ACCTCOLUMNDEF
entry?
Thanks in advance.
Brian Morris
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
--
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 [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
--
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 [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
