Thanks for your answer. I am looking for redundancy, if SQL does not work I can count on detail files. If the SQL problem blocks the whole FreeRADIUS server I think there is a problem of design (might be resolved in later version?). You may answer "work-as-design", but could you confirm? Why there is no protection against blocked SQL server to let FreeRADIUS process queries ? Considering that, would you advise another configuration? Thanks AL Le 12 févr. 2014 à 14:54, Alan DeKok <aland@deployingradius.com> a écrit :
Aurélien Lafranchise wrote:
Sorry I mixed up some stuff. Start and Stop records are handle the same on my configuration. During the database problem start records went properly in detail files but not stop records. Why?
Perhaps you could try reading my messages. I've been trying to answer this.
In the previous email, you tell me that there is no impact on detail files if the database goes down and you tell me now that it can be have an impact. I am a bit lost.
You're looking for inconsistencies where there is none. You're not reading my messages and taking them at face value. You're interpreting them through your ideas as to how the server works.
The modules are independent. If "detail" is listed before "sql", it will ALWAYS log to "detail", even if there's a problem with "sql". However, if the SQL server is *blocked* rather than *down*, it will also block FreeRADIUS. It will block *all* threads in FreeRADIUS, and the server will not be able to process *anything*.
My answer to these issues is always the same. If you have problems with SQL, go fix SQL. Stop trying to "fix" FreeRADIUS when there's nothing wrong with it.
If the dashboard on your car says "no fuel", you re-fuel it. You don't claim that the dashboard is broken.. and replace the dashboard.
The same applies here. SQL is broken. No amount of posting to this list about FreeRADIUS will fix your SQL server. Fix the real problem.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html