FR behavior when DB not available

Anatoliy cphlpd at gmail.com
Wed Jul 19 12:37:01 UTC 2023


Hi Alan , DB that never goes down - is fantastic. At least while customer
is understand that investment in DB (which will never goes down) will never
payback.

On Wed, Jul 19, 2023 at 6:04 PM Alan DeKok <aland at deployingradius.com>
wrote:

> On Jul 19, 2023, at 2:25 AM, Anatoliy <cphlpd at gmail.com> wrote:
> > With this configuration, I can , for example, mark DB failed , before MW
> .
> > and this will prevent unnecessary connections to DB that will fail...
>
>   This helps a little bit, but it doesn't help when connections are
> blocked.
>
>   The only real solution is to not have the DB go down.  While this may
> seem extreme, I would also suggest that it's a little weird to make
> FreeRADIUS depend on the DB, and then have the DB randomly go away.
>
>   The effort should put into making sure the DB doesn't go down.  Patching
> around an unstable DB by poking FreeRADIUS is like putting a tiny bandaid
> on a large injury.  The bandaid may be pretty but it's not going to do a
> whole lot.
>
>   Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>


More information about the Freeradius-Users mailing list