redundant block in CVS 2006-11-16

freeradius at list.coretech.ro freeradius at list.coretech.ro
Thu Nov 16 22:51:43 CET 2006


hello,

I am trying to switch from cvs version 2006-08-24 to cvs version 
2006-11-16 and my accounting redundant group is processing the second 
module even if the first one is returning ok. why is detail_fail 
processed if sql returns ok ?

Is something (I do not find in doc / changelog) changed ?

thanks,
Razvan Radu

radiusd.conf:
accounting {
        detail
        redundant {
                sql
                detail_fail
        }
}

radiusd -X
  Processing the accounting section of radiusd.conf
modcall:  entering group accounting for request 14
radius_xlat:  '/acct/freeradius/accounting_full/192.168.0.1/20061116'
rlm_detail: /acct/freeradius/accounting_full/%{Client-IP-Address}/%Y%m%d 
expands to /acct/freeradius/accounting_full/192.168.0.1/20061116
radius_xlat:  'Thu Nov 16 19:15:44 2006'
  modcall[accounting]: module "detail" returns ok for request 14
modcall:   entering group  for request 14
radius_xlat:  ' ... LONG SQL QUERY ...'
rlm_sql (sql): Reserving sql socket id: 46
rlm_sql_postgresql: Status: PGRES_COMMAND_OK
rlm_sql_postgresql: query affected rows = 1 , fields = 1
rlm_sql (sql): Released sql socket id: 46
  modcall[accounting]: module "sql" returns ok for request 14
radius_xlat:  '/acct/freeradius/accounting_fail/192.168.0.1/1163697344'
rlm_detail: /acct/freeradius/accounting_fail/%{Client-IP-Address}/%l 
expands to /acct/freeradius/accounting_fail/192.168.0.1/1163697344
radius_xlat:  'Thu Nov 16 19:15:44 2006'
  modcall[accounting]: module "detail_fail" returns ok for request 14
modcall:  group  returns ok for request 14
modcall: group accounting returns ok for request 14
Sending Accounting-Response of id 85 to 192.168.0.1 port 23148
Finished request 14







More information about the Freeradius-Users mailing list