On Jul 9, 2019, at 1:08 PM, R3DNano <r3dnano@gmail.com> wrote:
I really appreciate this reply and after some time, I still can't figure out how to work around this issue.
Keep the database up. There's just no reason to take a critical DB down for hours.
While, I of course won't/can't blame it on freeradius, I'd like to ask if any of you guys deal in any way with sql server failures in any way, of course, externally.
We bring the DB back up.
Maybe there's some kind of script/solution to automagically detect the sql server failure and modify the server logic on the go?
No. We bring the DB back up.
I really can't think of a way and perhaps what I'm asking is impossible. Just wanting to check up with you guys before completely discarding the option.
If the DB is not local to the RADIUS server, then create a local slave. And make sure that the slave stays up. Alan DeKok.