Okay for me this is a 99% solution. I use now value is 1 Thanks again i am very happy now...
Michel > It isn't a solution but an ugly hack :) > > Em Qui, 2005-02-10 �s 20:44 +0100, Michel van Dop escreveu: > > Hi, > > > > This is the solution for slow redundant mysql authorize: > > > > echo 0 > /proc/sys/net/ipv4/tcp_syn_retries > > (default value is 5) > > > > Thanks to Tiago > > > > Micheld > > > > ----- Original Message ----- > > From: "Michel van Dop" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Thursday, February 10, 2005 3:30 PM > > Subject: Re: Redundant mysql authorize not working > > > > > > > Hi Gilbert, > > > > > > I am not sure but i think also this is a bug im mysql driver! > > > Same problems here! But i have a little solution i hope this > > > is working on your situation. > > > We have two location and every location have a own radius server and ow> > > > n > > > mysql db. > > > We also use mysql replication. So there is a master en slave situation. > > > > > > On location one we have master db and radius. > > > On radiusd.conf we have > > > authorize > > > redundant { > > > sql1 #(masterdb on localdb) > > > sql2 #(slave db on location 2) > > > } > > > > > > > > > accounting { > > > sql1 #(location 1 master) > > > > > > > > > On location 2: > > > radiusd.conf we have: > > > authorize > > > redundant { > > > sql2 #(slave db localdb) > > > sql1 #(masterdb db on location 2) > > > } > > > > > > accounting { > > > sql1 #(location 1 master) > > > > > > So radius server on more than one location check to login in the local > > > > db > > > (accounting). > > > So the users can login every time local. > > > On the client NAS we use chillipot so there we can configure a first > > > radius and second. > > > So first is local same subnet and when down he go to the second radius > > > > i > > > can connection to location 2. > > > > > > So i think this is save (for me) !? > > > I testit and i can reboot one of the radius servers and every users can> > > > login in the down time. > > > > > > The best solution is when redundant is fast working. But i have spent s> > > > o > > > much time in it. > > > This is for my a working solution. > > > Sorry for my english! > > > > > > Michel > > > > > >> Nobody can help me or can say this is a bug? > > >> max_request_time make no different.. > > >> > > >> Gilbert > > >> > > >> > what happens... > > >> > > > >> > The connection to the second mysql database it takes three minutes! > > >> > > > >> > It look likes a bug i search on google and see same problems but no > > >> > solutions! > > >> > > > >> > I set max_request_time to 5 seconds, so it's faster for testing: > > >> > > > >> > Gilbert > > >> > > > >> > > Gilbert Otingen <[EMAIL PROTECTED]> wrote: > > >> > > > redundant { > > >> > > > sql1 > > >> > > > sql2 > > >> > > > } > > >> > > > > > >> > > > And i can see the successful connect in the log and everything > > >> > > > works as > > >> > > > expected... but until i shutdown the first database. > > >> > > > > >> > > Then... what happens? > > >> > > > > >> > > > Any ideas on what the problem is? > > >> > > > > >> > > Without a description of the problem, I have no idea. > > >> > > > > >> > > Alan DeKok. > > >> > > > > >> > > - > > >> > > 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 > > > Met vriendelijke groet, > > > > > > M. v Dop > > > www.westwireless.nl > > > > > > - > > > 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 Met vriendelijke groet, M. v Dop www.westwireless.nl - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
