One more thing related to SQL accounting...
Everytime I received error "Stop packet with zero session length"... Accounting will be stored in both sql1 & sq2.. please refer debug log..
should I change noop=xxxx to something else instead of below...???
--haizam
group { sql1 { fail=1 notfound=return noop=2 ok=return updated=3 reject=return userlock=4 invalid=5 handled=6 } sql2 { < same as above> } }
##################################
radius_xlat: 'UPDATE radacct SET AcctStopTime = '2005-01-18 10:39:34', AcctSessionTime = '', AcctInputOctets =
'', AcctOutputOctets = '', AcctTerminateCause = '', AcctStopDelay = '0', ConnectInfo_stop = '' WHERE AcctSessi
onId = '442225381' AND UserName = '' AND NASIPAddress = '161.142.17.2''
rlm_sql (sql1): Reserving sql socket id: 4
radius_xlat: 'rlm_sql: Stop packet with zero session length. (user '', nas '161.142.17.2')'
rlm_sql: Stop packet with zero session length. (user '', nas '161.142.17.2')
rlm_sql (sql1): Released sql socket id: 4
radius_xlat: 'INSERT into radacct (AcctSessionId, AcctUniqueId, UserName, Realm, NASIPAddress, NASPortId, NASP
ortType, AcctStartTime, AcctStopTime, AcctSessionTime, AcctAuthentic, ConnectInfo_start, ConnectInfo_stop, Acct
InputOctets, AcctOutputOctets, CalledStationId, CallingStationId, AcctTerminateCause, ServiceType, FramedProtoc
ol, FramedIPAddress, AcctStartDelay, AcctStopDelay) values('442225381', '18e9d9976b13739f', '', '', '161.142.17
.2', '10202', 'Sync', DATE_SUB('2005-01-18 10:39:34', INTERVAL (0 + 0) SECOND), '2005-01-18 10:39:34', '', '',
'', '', '', '', '9915600', '0320529716', '', '', '', '', '0', '0')'
rlm_sql (sql1): Released sql socket id: 4
modcall[accounting]: module "sql1" returns noop for request 132
radius_xlat: ''
radius_xlat: 'UPDATE radacct SET AcctStopTime = '2005-01-18 10:39:34', AcctSessionTime = '', AcctInputOctets =
'', AcctOutputOctets = '', AcctTerminateCause = '', AcctStopDelay = '0', ConnectInfo_stop = '' WHERE AcctSessi
onId = '442225381' AND UserName = '' AND NASIPAddress = '161.142.17.2''
rlm_sql (sql2): Reserving sql socket id: 4
radius_xlat: 'rlm_sql: Stop packet with zero session length. (user '', nas '161.142.17.2')'
rlm_sql: Stop packet with zero session length. (user '', nas '161.142.17.2')
rlm_sql (sql2): Released sql socket id: 4
radius_xlat: 'INSERT into radacct (AcctSessionId, AcctUniqueId, UserName, Realm, NASIPAddress, NASPortId, NASP
ortType, AcctStartTime, AcctStopTime, AcctSessionTime, AcctAuthentic, ConnectInfo_start, ConnectInfo_stop, Acct
InputOctets, AcctOutputOctets, CalledStationId, CallingStationId, AcctTerminateCause, ServiceType, FramedProtoc
ol, FramedIPAddress, AcctStartDelay, AcctStopDelay) values('442225381', '18e9d9976b13739f', '', '', '161.142.17
.2', '10202', 'Sync', DATE_SUB('2005-01-18 10:39:34', INTERVAL (0 + 0) SECOND), '2005-01-18 10:39:34', '', '',
'', '', '', '', '9915600', '0320529716', '', '', '', '', '0', '0')'
rlm_sql (sql2): Released sql socket id: 4
modcall[accounting]: module "sql2" returns noop for request 132
modcall: group group returns noop for request 132
modcall: group accounting returns ok for request 132
Sending Accounting-Response of id 101 to 161.142.17.2:1027
Finished request 132
Going to the next request
###########################################
----- Original Message ----- From: "Alan DeKok" <[EMAIL PROTECTED]>
To: <freeradius-users@lists.freeradius.org>
Sent: Tuesday, January 18, 2005 00:40
Subject: Re: SQL db failover
"Rohaizam Abu Bakar" <[EMAIL PROTECTED]> wrote:But before that.. I tried to use the simplified one using "redundant" as below:-
redundant { sql1 sql2 }
But seems everytime accounting record being sent.. I will store in both of
the mysql server... not the first one that return OK.. why???
It's a known bug. See bugs.freeradius.org
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html