Re: SQL db failover

2005-01-26 Thread Nicolas Baradakis
Rohaizam Abu Bakar wrote: How can we possible do to ensure only when sql1 down.. then the accounting will be sent to sql2..?? You might try a different approach: - store accounting in detail files (man rlm_detail) - run radsqlrelay to send accounting in the database (get it from a

Re: SQL db failover

2005-01-25 Thread Rohaizam Abu Bakar
24, 2005 19:16 Subject: Re: SQL db failover Rohaizam Abu Bakar wrote: How can we possible do to ensure only when sql1 down.. then the accounting will be sent to sql2..?? You might try a different approach: - store accounting in detail files (man rlm_detail) - run radsqlrelay to send accounting

Re: SQL db failover

2005-01-24 Thread Nicolas Baradakis
Rohaizam Abu Bakar wrote: How can we possible do to ensure only when sql1 down.. then the accounting will be sent to sql2..?? You might try a different approach: - store accounting in detail files (man rlm_detail) - run radsqlrelay to send accounting in the database (get it from a CVS

Re: SQL db failover

2005-01-20 Thread Rohaizam Abu Bakar
to different mysql thanks.. --haizam - Original Message - From: Rohaizam Abu Bakar [EMAIL PROTECTED] To: freeradius-users@lists.freeradius.org Sent: Tuesday, January 18, 2005 11:30 Subject: Re: SQL db failover One more thing related to SQL accounting... Everytime I received error

Re: SQL db failover

2005-01-17 Thread Alan DeKok
Rohaizam Abu Bakar [EMAIL PROTECTED] wrote: But before that.. I tried to use the simplified one using redundant as below:- redundant { sql1 sql2 } But seems everytime accounting record being sent.. I will store in both of the mysql server... not the first one that return OK..

Re: SQL db failover

2005-01-17 Thread Rohaizam Abu Bakar
### - Original Message - From: Alan DeKok [EMAIL PROTECTED] To: freeradius-users@lists.freeradius.org Sent: Tuesday, January 18, 2005 00:40 Subject: Re: SQL db failover Rohaizam Abu Bakar [EMAIL PROTECTED] wrote: But before that.. I tried to use the simplified one using redundant as below

Re: SQL db failover

2005-01-16 Thread Alan DeKok
Michel van Dop [EMAIL PROTECTED] wrote: Okay good, i replace any refrence to sql module and fix it. But how do i replace this? In group or sql1,sql2 or ? You probably want the group. What's the name of sql1 and sql2 ? sql1 and sql2. Alan DeKok. - List info/subscribe/unsubscribe? See

Re: SQL db failover

2005-01-16 Thread Rohaizam Abu Bakar
portion ?? redundant { sql1 sql2 handled } always handled{ rcode = handled } --haizam - Original Message - From: Michel van Dop [EMAIL PROTECTED] To: freeradius-users@lists.freeradius.org Sent: Sunday, January 16, 2005 08:04 Subject: Re: SQL db failover It works!! Yes Thanks

Re: SQL db failover

2005-01-15 Thread Michel van Dop
@lists.freeradius.org Sent: Saturday, January 15, 2005 1:26 AM Subject: Re: SQL db failover Michel van Dop [EMAIL PROTECTED] wrote: So i leave the default config in radiusd.conf include the file sql.conf and put this in my radiusd.conf: $INCLUDE ${confdir}/sql.conf modules { Once again, the include for sql.conf

Re: SQL db failover

2005-01-15 Thread Michel van Dop
Hi, I have to run TWO MySQL servers and have FreeRadius fall over between them modules { # same place where this $INCLUDE ${confdir}/sql.conf $INCLUDE ${confdir}/sql1.conf $INCLUDE ${confdir}/sql2.conf On 'authorize' section of radiusd.conf i change the 'sql' entry to a 'group' one: group

Re: SQL db failover

2005-01-15 Thread Alan DeKok
Michel van Dop [EMAIL PROTECTED] wrote: Okay i understand that ( i hope so): Now i do this in radiusd.conf: Yup, that should work. I get this error cat /var/log/radius/radius.log Sat Jan 15 13:35:19 2005 : Error: ERROR: Cannot find a configuration entry for module sql. Some part of

Re: SQL db failover

2005-01-15 Thread Michel van Dop
15, 2005 5:58 PM Subject: Re: SQL db failover Michel van Dop [EMAIL PROTECTED] wrote: Okay i understand that ( i hope so): Now i do this in radiusd.conf: Yup, that should work. I get this error cat /var/log/radius/radius.log Sat Jan 15 13:35:19 2005 : Error: ERROR: Cannot find a configuration

Re: SQL db failover

2005-01-15 Thread Michel van Dop
Subject: Re: SQL db failover Okay good, i replace any refrence to sql module and fix it. But how do i replace this? In group or sql1,sql2 or ? What's the name of sql1 and sql2 ? Thank you, Michel - Original Message - From: Alan DeKok [EMAIL PROTECTED] To: freeradius-users

SQL db failover

2005-01-14 Thread Michel van Dop
Hi, The mirroring between the two mysql db (3.23.58-4) work with the replication mechanism of mysql and I have two sql.conf to describe the way to connect to each db and right config on radiusd.conf I use freeradius-0.9.3-1.1 and freeradius-mysql-0.9.3-1.1 I now this is old but this is the last

Re: SQL db failover

2005-01-14 Thread Alan DeKok
Michel van Dop [EMAIL PROTECTED] wrote: I use freeradius-0.9.3-1.1 and freeradius-mysql-0.9.3-1.1 I now this is old but this is the last stap! I would suggest upgrading. See http://www.freeradius.org/security.html I have this in the radiusd.conf $INCLUDE ${confdir}/sql.conf $INCLUDE

Re: SQL db failover

2005-01-14 Thread Michel van Dop
Thank you Alan, Sorry but this is new for me. Freeradius is now running but on one db. Now the last step freeradius SQL db failover! So i leave the default config in radiusd.conf include the file sql.conf and put this in my radiusd.conf: $INCLUDE ${confdir}/sql.conf modules { sql sql1

Re: SQL db failover

2005-01-14 Thread Alan DeKok
Michel van Dop [EMAIL PROTECTED] wrote: So i leave the default config in radiusd.conf include the file sql.conf and put this in my radiusd.conf: $INCLUDE ${confdir}/sql.conf modules { Once again, the include for sql.conf MUST BE INSIDE of the modules section. It's there in the

Re: SQL db failover

2004-09-30 Thread Edgars
ok, thanks for the input. So, what can someone suggest what configuration should i add only for such a case: if sql1 is down then go and search for the user to sql2? Edgars Alan DeKok wrote: Cris Boisvert [EMAIL PROTECTED] wrote: $INCLUDE ${confdir}/sql.conf $INCLUDE ${confdir}/sql2.conf

Re: SQL db failover

2004-09-30 Thread Kostas Kalevras
On Thu, 30 Sep 2004, Edgars wrote: ok, thanks for the input. So, what can someone suggest what configuration should i add only for such a case: if sql1 is down then go and search for the user to sql2? Your question has already been answered. Just replace accounting with authorize. authorize{

RE: SQL db failover

2004-09-29 Thread Kostas Kalevras
On Tue, 28 Sep 2004, Paul wrote: What i need is failover for accounting and session tracking. Auth will be done using LDAP. Mirroring the DB is not possibe because accounting has alot of inserts, that would need to have multi-master replication. I would like to use application data

Re: SQL db failover

2004-09-29 Thread Edgars
i'm also trying to make this configuration. But something doesn't stick together. i've added the following lines in the modules section: sql sql1 { } sql sql2 { } but when starting the server the following appears: Module: Instantiated preprocess (preprocess) radiusd.conf[11]

Re: SQL db failover

2004-09-29 Thread Alan DeKok
Cris Boisvert [EMAIL PROTECTED] wrote: I have been trying to do the same thing I have the references in the radius.conf as notated in the Doc's although I cannot get it to Connect to the second sql server I have this in the radius.conf $INCLUDE ${confdir}/sql.conf $INCLUDE

RE: SQL db failover

2004-09-29 Thread Cris Boisvert
Yup thats what I'm getting also... now.. I'm glad I'm not alone -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edgars Sent: Wednesday, September 29, 2004 11:30 AM To: [EMAIL PROTECTED] Subject: Re: SQL db failover i'm also trying to make

RE: SQL db failover

2004-09-29 Thread Paul
On Wed, 2004-09-29 at 08:55, Kostas Kalevras wrote: On Tue, 28 Sep 2004, Paul wrote: What i need is failover for accounting and session tracking. Auth will be done using LDAP. Mirroring the DB is not possibe because accounting has alot of inserts, that would need to have

RE: SQL db failover

2004-09-29 Thread Kostas Kalevras
On Wed, 29 Sep 2004, Paul wrote: On Wed, 2004-09-29 at 08:55, Kostas Kalevras wrote: On Tue, 28 Sep 2004, Paul wrote: What i need is failover for accounting and session tracking. Auth will be done using LDAP. Mirroring the DB is not possibe because accounting has alot of

RE: SQL db failover

2004-09-29 Thread Cris Boisvert
I have this in my radiusd.conf now. I get this error when I try to start radius Wed Sep 29 12:00:27 2004 : Info: rlm_sql_mysql: Starting connect to MySQL server for #0 Wed Sep 29 12:00:27 2004 : Info: rlm_sql_mysql: Starting connect to MySQL server for #1 Wed Sep 29 12:00:27 2004 : Info:

RE: SQL db failover

2004-09-29 Thread Kostas Kalevras
On Wed, 29 Sep 2004, Cris Boisvert wrote: I have this in my radiusd.conf now. I get this error when I try to start radius Wed Sep 29 12:00:27 2004 : Info: rlm_sql_mysql: Starting connect to MySQL server for #0 Wed Sep 29 12:00:27 2004 : Info: rlm_sql_mysql: Starting connect to MySQL

Re: SQL db failover

2004-09-29 Thread Alan DeKok
Cris Boisvert [EMAIL PROTECTED] wrote: $INCLUDE ${confdir}/sql.conf $INCLUDE ${confdir}/sql2.conf modules { sql sql { } sql sql2 { } The $INCLUDE ${confdir}/sql.conf should be INSIDE of the modules{} section, which means you don't need to have TWO definitions

RE: SQL db failover

2004-09-29 Thread Cris Boisvert
Of Kostas Kalevras Sent: Wednesday, September 29, 2004 12:33 PM To: [EMAIL PROTECTED] Subject: RE: SQL db failover On Wed, 29 Sep 2004, Cris Boisvert wrote: I have this in my radiusd.conf now. I get this error when I try to start radius Wed Sep 29 12:00:27 2004 : Info: rlm_sql_mysql: Starting

SQL db failover

2004-09-28 Thread Paul
Hi folks. We need to have a 2 server deployment with accounting and session tracking using an SQL db (mysql or postgres). What i would like to do is: - Each server has a local DB running - Both DB's should have data synchronized for sessino tracking - All accounting is written to local DB and

SQL db failover

2004-09-28 Thread EROS
config on radiusd.conf to tell it how using this two db. If you want some more help ask ... :] -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Paul Envoyé : mardi 28 septembre 2004 18:12 À : [EMAIL PROTECTED] Objet : SQL db failover Hi folks. We need

RE: SQL db failover

2004-09-28 Thread Cris Boisvert
not worried about that for now.. Thanx -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EROS Sent: Tuesday, September 28, 2004 12:53 PM To: [EMAIL PROTECTED] Subject: SQL db failover In doc/configurable_failover you have your answer. I've tried the same

RE: SQL db failover

2004-09-28 Thread Paul
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EROS Sent: Tuesday, September 28, 2004 12:53 PM To: [EMAIL PROTECTED] Subject: SQL db failover In doc/configurable_failover you have your answer. I've tried the same schema you wanna do

RE: SQL db failover

2004-09-28 Thread Paul
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EROS Sent: Tuesday, September 28, 2004 12:53 PM To: [EMAIL PROTECTED] Subject: SQL db failover In doc/configurable_failover you have your answer. I've tried the same schema you wanna do and it works perfectly The mirroring between