> Hi,
Hi Stella,
I ran in your problem just quite weeks ago and I solved this way:
- Use mysql replication for syncing the two database (you have to make
db1 slave of db2 and db2 slave of db1: every record inserted in one db
will be automatically inserted in the other one)
- Use heartbeat (or what
I'm sure that would work if they were normal (non-radius) records in a
database. The problem is there are two accounting records (stop and start).
When radius receives a start record it just inserts it into the database
(easy) but when it receives a stop record, it tries to find the original
start
Given my levels of FreeRADIUS knowledge vs MySQL, I would go with a
database-level approach :-)
What version of MySQL are you using - you could maybe cluster the databases?
Alternatively have RADIUS write to one database and use MySQL Proxy to
handle the two databases if you dont want to cluster
Hi,
We're setting up two radius servers and configuring them so the accounting
records are inserted into a mysql database. For redundancy, we're having two
radius servers and two database servers. Both radius servers will attempt to
write the records to the primary database, if that fails, the s
4 matches
Mail list logo