On Tue, 1 Feb 2005, Michel van Dop wrote: > When i only connect freeradius to the slave db it works great! Same on only > master db! > I think there is a radiusd.conf problem i find on google more configs > old/and very old but not a working solution. > The fail-over document on the own radius directory is very old from 2000. > > Okay thank you for the radrelay tip. Is there i example or document for > this? > And when i use radrelay is there a option to set only master db to write > sessions on finisch sessions? > Or radrelay working only for account reading?
Check out doc/radrelay, it will show you how to use it. You will set it up to send to a certain server, so in your case you just point it at your master accounting server. The replication setup between your master and slave sql database will take care of replicating the data to the slave. > > ----- Original Message ----- > From: "Dustin Doris" <[EMAIL PROTECTED]> > To: <freeradius-users@lists.freeradius.org> > Sent: Tuesday, February 01, 2005 4:08 PM > Subject: Re: Fail_over mysql again! > > > > > >> Hello, > >> > >> I have problems on FC1 freeradius 0.9.3 on failover and mysql db's. I use > >> two mysql db's replication. One master db and slave db. > >> So when master is down freeradius server go on on the second slave db > >> whit accounting. > >> > >> So i think there is a bug in version 0.9.3 or sql/driver/module. > >> > >> Now i install two machines FC2 whit: > >> freeradius-1.0.1-0.FC2 and freeradius-mysql-1.0.1-0.FC2 > >> But same problems on fail_over on sql1 and sql2. Sql1 is down and second > >> db, sql2 is up. > >> Start slow and user request hi give every 240 second a good replay. > >> When i start the first db everithing works!!! ? > >> > >> So can some one send me good sample or tips how to use fail_over mysql > >> on 2 db's. It's only for accounting so users get a replay when masterdb > >> is down. > >> > >> Michel > >> > > > > How does it perform when you have it only talking to the slave server? > > For example, if you just take out the redundancy and setup to only use the > > slave/failover server for sql? Is it fast then or do you see a similar > > slow startup and query issues? > > > > Another option, is what I do, is use radrelay to send the accounting > > packets to the sql database. That way the radius server just logs to a > > detail file, which is quick, and the accounting packet is done. Then > > radrelay constantly tries to send those accounting packets over to our sql > > server for storage. With that you can afford some downtime on the sql > > server, because as soon as it comes back up, radrelay will send over all > > the missed packets. When everything is up, the accounting packets are > > pretty close to real-time in the sql server. I guess it depends how close > > to real-time you need in the sql database. > > > > BTW. I'm not saying to stop trying to make failover work, just offering > > another option to it, if you can't get it to work. > > > > -Dusty > > > > > > > > - > > List info/subscribe/unsubscribe? See > > http://www.freeradius.org/list/users.html > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
