Problem with accounting insert into Oracle

Aurélien Lafranchise aurelien.lafranchise at mobiquithings.com
Mon Aug 13 14:25:27 CEST 2012


It seems that Freeradius is getting stuck when inserting hex chain. Does that remind something to someone ?

AL

Le 13 août 2012 à 13:42, Aurélien Lafranchise a écrit :

> Hi,
> 
> I have the same error for every request in dialup.conf (STOP, START, UPDATE).
> 
> The database connection is working well but I have:
> [sql] Couldn't insert SQL accounting STOP record - ORA-01756: quoted string not properly terminated 
> 
> with sqltrace on you can see the mistake at the end. The request seems to be truncated:
> INSERT into radacct (RadAcctId, AcctSessionId, AcctUniqueId, UserName, Realm, NASIPAddress, NASPortId, NASPortType, AcctStartTime, AcctStopTime, AcctSessionTime, AcctAuthentic, ConnectInfo_start, ConnectInfo_stop, AcctInputOctets, AcctOutputOctets, CalledStationId, CallingStationId, AcctTerminateCause, ServiceType, FramedProtocol, FramedIPAddress, AcctStartDelay, AcctStopDelay, IMSI_3GPP, ChargingID_3GPP, PDPType_3GPP, ChargingGwAddress_3GPP, GPRSNegotiatedQoSprofile_3GPP, SGSNAddress_3GPP, GGSNAddress_3GPP, IMSIMCCMNC_3GPP, GGSNMCCMNC_3GPP, NSAPI_3GPP, SessionStopIndicator_3GPP, SelectionMode_3GPP, ChargingCharacteristics_3GPP, ChargingGwIPv6Address_3GPP, SGSNIPv6Address_3GPP, GGSNIPv6Address_3GPP, IPv6DNSServers_3GPP, SGSNMCCMNC_3GPP, TeardownIndicator_3GPP, IMEISV_3GPP, RATType_3GPP, MSTimeZone_3GPP, CamelChargingInfo_3GPP, PacketFilter_3GPP, NegotiatedDSCP_3GPP, AllocateIPType_3GPP) 	VALUES('', 'D4090646343006F3', '64e5c1c4162df0d5', '447937700458', '', 	'10.100.100.3', '', 'Ethernet', NULL, TO_DATE('2012-08-13 11:35:27','yyyy-mm-dd hh24:mi:ss'), 	'74', 'RADIUS', '', '', 	'679' + ('0' * 4294967296),         '83' +  ('0' * 4294967296),         'internet.mbqt.net', '447937700458', 'User-Request', 'Framed-User',         'GPRS-PDP-Context', '10.73.248.60', '0', '0', '234507089001283', '875562739', '0', '', '98-1B631F', '80.10.0.97', '212.9.6.70', '23450', '', '5', '255', '0', '0800', '', '', '', '', '20801', '', '', '2', ';
> 
> but in the dialup.conf file it is ok:
> accounting_stop_query_alt = "INSERT into ${acct_table2} (RadAcctId, AcctSessionId, AcctUniqueId, UserName, Realm, NASIPAddress, NASPortId, NASPortType, AcctStartTime, AcctStopTime, AcctSessionTime, AcctAuthentic, ConnectInfo_start, ConnectInfo_stop, AcctInputOctets, AcctOutputOctets, CalledStationId, CallingStationId, AcctTerminateCause, ServiceType, FramedProtocol, FramedIPAddress, AcctStartDelay, AcctStopDelay, IMSI_3GPP, ChargingID_3GPP, PDPType_3GPP, ChargingGwAddress_3GPP, GPRSNegotiatedQoSprofile_3GPP, SGSNAddress_3GPP, GGSNAddress_3GPP, IMSIMCCMNC_3GPP, GGSNMCCMNC_3GPP, NSAPI_3GPP, SessionStopIndicator_3GPP, SelectionMode_3GPP, ChargingCharacteristics_3GPP, ChargingGwIPv6Address_3GPP, SGSNIPv6Address_3GPP, GGSNIPv6Address_3GPP, IPv6DNSServers_3GPP, SGSNMCCMNC_3GPP, TeardownIndicator_3GPP, IMEISV_3GPP, RATType_3GPP, MSTimeZone_3GPP, CamelChargingInfo_3GPP, PacketFilter_3GPP, NegotiatedDSCP_3GPP, AllocateIPType_3GPP) \
> 	VALUES('', '%{Acct-Session-Id}', '%{Acct-Unique-Session-Id}', '%{SQL-User-Name}', '%{Realm}', \
> 	'%{NAS-IP-Address}', '%{NAS-Port-Id}', '%{NAS-Port-Type}', NULL, TO_DATE('%S','yyyy-mm-dd hh24:mi:ss'), \
> 	'%{Acct-Session-Time}', '%{Acct-Authentic}', '', '%{Connect-Info}', \
> 	'%{Acct-Input-Octets}' + ('%{%{Acct-Input-Gigawords}:-0}' * 4294967296), \
>        '%{Acct-Output-Octets}' +  ('%{%{Acct-Output-Gigawords}:-0}' * 4294967296), \
>        '%{Called-Station-Id}', '%{Calling-Station-Id}', '%{Acct-Terminate-Cause}', '%{Service-Type}', \
>        '%{Framed-Protocol}', '%{Framed-IP-Address}', '0', '%{Acct-Delay-Time:-0}', '%{3GPP-IMSI}', '%{3GPP-Charging-ID}', '%{3GPP-PDP-Type}', '%{3GPP-Charging-Gateway-Address}', '%{3GPP-GPRS-Negotiated-QoS-profile}', '%{3GPP-SGSN-Address}', '%{3GPP-GGSN-Address}', '%{3GPP-IMSI-MCC-MNC}', '%{3GPP-GGSN-MCC-MNC}', '%{3GPP-NSAPI}', '%{3GPP-Session-Stop-Indicator}', '%{3GPP-Selection-Mode}', '%{3GPP-Charging-Characteristics}', '%{3GPP-Charging-Gateway-IPv6-Address}', '%{3GPP-SGSN-IPv6-Address}', '%{3GPP-GGSN-IPv6-Address}', '%{3GPP-IPv6-DNS-Servers}', '%{3GPP-SGSN-MCC-MNC}', '%{3GPP-Teardown-Indicator}', '%{3GPP-IMEISV}', '%{3GPP-RAT-Type}', '%{3GPP-MS-TimeZone}', '%{3GPP-Camel-Charging-Info}', '%{3GPP-Packet-Filter}', '%{3GPP-Negotiated-DSCP}', '%{3GPP-Allocate-IP-Type}')"
> 
> Any idea ? Is there a global option for the maximum number of characters for a request ?
> 
> Cheers
> Aurélien Lafranchise

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20120813/61d511f3/attachment-0001.html>


More information about the Freeradius-Users mailing list