I want to keep NAS table replicated in redundant SQL servers for failover reasons, is this fair? Now, if NAS is kept only in one SQL server this will become a single point of failure and if this particular DB fails then radius application cannot just seemlessly failover to another redundant DB server because NAS table can exist only on one DB server because of freeradius design/limitation.
How do you propose solving SQL NAS table replication challenge? I understand that you can tell me keeping NAS info in local flat file(clients.conf) and do not reply on database. Then I'll need scripting on every radius server periodically connecting to DB and generating NAS (clients.conf) on the fly and HUP the radiusd or do not rely on database and hand edit clients.conf file and rsync it. But it would be nice to keep NAS information in DB but also have sql redundancy. Thanks again for you reply. tnt-4 wrote: > >>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? >> > > Why is this "a problem"? > > 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-tp22413666p22425466.html Sent from the FreeRadius - User mailing list archive at Nabble.com. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
