Thanks for your reply, Alan. Downtime could happen sometimes and I understand I can just comment out a module when the SQL server goes down, but sometimes it could be out of our control, a database can fail for hours and I thought there might be a way freeradius can just "deal" with failed mysql connections by rejecting if the source is unavailable.... I don't mean that freeradius "should" deal with it, by any means, just to have the option of rejecting if the auth source is unreachable. Does this mean the same behavior can be expected if I'm authenticating against LDAP and the LDAP server goes temporarily down? Thanks again On Thu, Apr 4, 2019 at 9:55 PM Alan DeKok <aland@deployingradius.com> wrote:
On Apr 4, 2019, at 3:50 PM, R3DNano <r3dnano@gmail.com> wrote:
Some of my auth sources are oracle databases via linux odbc. At some point, those databases might become unreachable for some external reason, freeradius then enters and stays in a failed state, trying to stablish the connection.
That's the way the server is supposed to work.
Is there a way to just reject the authentication if the source is unavailable and prevent the server failure? Is this working as intended?
If you don't want the server to use a module, then you can remove that module from the server configuration.
If you want the server to use a module, then you should ensure that the module works. And for SQL, ensure that the SQL database stays up.
It doesn't make any sense to configure FreeRADIUS to use SQL, and then leave SQL down for days.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html