First of all, thank you for your quick answer. I just had a look at "buffered-sql virtual server" and it seems to be a solution.
Anyway, I would really prefer to find out the way to tell the freeradius to stop waiting for the database and keeping my current configuration. Indeed, I have already configured the server and did some scripts in order to handle backup of accounting information. Right now my solution's philosophy is: log to database and alternatively to sql_log file with some automatic scripts which regularly check the sql_log file and database status to insert backup sql requests within. I would like to take advantage of the previous effort if possible. Antoine -----Message d'origine----- De : freeradius-users-bounces+antoine.jean-toussaint=bull....@lists.freeradius. org [mailto:freeradius-users-bounces+antoine.jean-toussaint=bull....@lists.fre eradius.org] De la part de Ivan Kalik Envoyé : lundi 20 juillet 2009 15:49 À : FreeRadius users mailing list Objet : Re: Accounting redundancy problem > I'm running Freeradius Version 2.0.4 with sql_postgres and sql_log > modules. > > Through the redundant module I can use a postgres database (on a remote > server) as a primary destination of my accounting messages and a sql_relay > file as an alternative in case of my database failure. > > > > Almost, everything works fine, meaning that if I stop the postgres process > on my remote server, freeradius try to send accounting messages to it and > as it receive messages from the server telling that the connection is > refused, freeradius logs accounting sql request into the sql_relay file. > > > > Now here's my problem: If I shutdown the server which host the postgres > database, freeradius try to send request to it and as there's no answer > from the server Freeradius doesn't pass through the SQL request through > the sql_log module. It keeps on waiting for an answer infinitely. > > > > When I launch freeradius whith the "freeradius -X" command, I can see the > following message: Error: rlm_sql (sql_TMS): Failed to connect DB handle > #0 > > > > It's very annoying because my backup solution doesn't handle the database > server unavailability! > > > > NB: I tried to use the "connect_failure_retry_delay" directive within the > rlm_sql_postgres module but this has no effect! Have a look at buffered-sql virtual server. Ivan Kalik Kalik Informatika ISP - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html