Hiya
I have setup redundant {} so that should the MySQL process on the system fail,
it fails back to a secondary server.
During testing I have noticed a slight log bug (possibly :) ). If 2 servers
are used sql1 and sql2, if during operation sql1 goes away and stops responding, the
daemon correctly tries to use it and fails over to sql2, and authorizes the login,
however it logs the connection error in the log file and also that it has rejected the
user (when it hasn't due to the second server working). Just a small thing
Another thing I have noticed is that if one of the servers is down when the
daemon starts, it never seems to try talking to that one again, even if the server
that was up should fail. So EG sql1 and sql2 again. sql1 is down at startup, daemon
uses sql2. sql1 then comes back up and shortly after sql2 dies, daemon now fails all
connections claiming the sql server is down, even tho sql1 is accepting connections.
What I did notice watching the logs was that SQL connections were established
to both SQL servers if they were availible. Does this mean that is sql1 becomes busy,
additional connections will be farmed off to sql2? If it does, then can this
behaviour be stopped until sql1 does fail?
Thanks again for your time.
--
-----
Graeme Hinchliffe (BSc)
Core Internet Systems Designer
Zen Internet (http://www.zen.co.uk)
ICQ 3842605 (link)
Sales : 0870 6000 971
Fax : 0870 6000 972
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
