Freeradius 2.1-1: failure modes

[leopold]

Thanks Ivan for your reply.
Regarding redundant databases:yes it can help because the problem will arise
only if all of them 
sql1,sql2,sql3 are not reachable or dead.
We are keeping NAS table in database and do not use flat files

I am having another issue with "readclients = yes" option
I can't keep this option set to yes in all 3 files:
sql1.conf,sql2.conf,sql3.conf

I want to keep NASes in the database and use DB replication to all 3
databases so all 3 databases have exact same mirrored data.

The problem happens that it cannot load NAS table from sql2 because of
duplicates taht it cached from sql1.

Here is the error I am getting:
rlm_sql (sql2): Failed to add client x.y.z.w (someclient) to clients list. 
Maybe there's a duplicate?

Is there any way around it other than using flat files for NAS?


tnt-4 wrote:
> 
>>Say I do not want to return reject in this case and I want the switch to
>>understand that radius is down and retry another radius server (a
>>backup/failover).
> 
> So call a script that executes killall radiusd - that should do it. But
> that's insane.
> 
>>Because if I return reject the NAS device treats this as radius is UP and
>>running.
> 
>>>But your radius server *is* up and running. sql module is not working. So
>>>fail-over to another sql server or users file.
> 
> If database is down or radius server cannot connect to the database then
> for all my purposes radius server is dead, because sql module is the heart
> of this solution and we do not use flat files at all.
> 
> 
> http://wiki.freeradius.org/Fail-over
> 
> Ivan Kalik
> Kalik Informatika ISP
> 
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
> 
> 

-- 
View this message in context: http://www.nabble.com/Freeradius-2.1-1%3A-failure-modes-tp22413666p22423224.html
Sent from the FreeRadius - User mailing list archive at Nabble.com.