ok i was getting crazy around here thought it was something about my configuration :) Good To know that Sql instances should have a variable that you can setup in case you are using a failover and it adjust some parameters like 1.- readclients: Actually i had to set the variable readclients to NO on one of my sql instances, i think it would be helpfull to set that on the radiusd.conf something like readclients = sql_redundant. 2.- sqlippool.conf: I think it wouldbe helpfull if sql-instance-name could be assigned from a redundant instance declared on the radiusd.conf Of course those are ideas i don't know you guys have more experience on this maybe mine are lame. Thanks for the Help. Rhommel Lamas. On Oct 27, 2010, at 4:17 PM, Alan DeKok wrote:
Rhommel Lamas wrote:
For example i have 2 Databases server, and 1 radius server, i need to configure it for failover. I already configured both Sql instances, and both sqlippool instances.
OK.
When i start radius i see two scenarios: 1.- If both Databases are up and running Radius Works.
That's the intent.
2.- If one of my mysql is down radius won't start because it fails to connect to the database that is down.
That's also the intent.
Is this the right way or i am failling on something?
It's the way it works now. We're looking into making it more flexible in the future.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html