Thankyou Alan! You gave us an idea about how we can set "ok" to return a default ok for the section.
We tested with our second approach as below and thrilled that it works/ This ensures radius returns ok even if the sql_update_**** modules fail. redundant{ ok } sql_update_xxxx { FAIL=1 } sql_update_yyyy { FAIL=1 } Regards Shweta On Sun, Dec 11, 2011 at 1:56 PM, Alan DeKok <al...@deployingradius.com>wrote: > Shweta Khadse wrote: > > The last two sql updates ie *"Sql_update_xxxx" and **"Sql_update_yyyy" > > *do not have a redundant module defined. The actions of these statement > > is not very critical. However we observe that if the radius is unable to > > execute these the radius drops the session and returns a FAIL. > > > > One way to avoid this session disconnection is to implement a redundant > > module for the last two statements as well. > > Yes. Just do: > > redundant { > sql_update_xxxx > sql_update_yyyy > ok > } > > 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