Igor-
It sounds like you are using the Oracle database for storing accounting data
only. If that is the case how about runnning an instance of Radiator on each
box for authentication and another instance of Radiator for accounting? That
way authentication should not be affected by database problems.
-Frank
-Original Message-
From: Igor Briski [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 4:06 AM
To: [EMAIL PROTECTED]
Subject: (RADIATOR) High availability radius
Hello!
We had some problems in the past regarding our main database server
(Oracle). The problem is, when the database slows down (it is still
accepting connections but runs very slow) Radiator starts slowing down
too and my NAS boxes eventually timeout. So all my users start getting
rejected.
Both of our Radiator servers connect to the same database, so we
generally have a single point of failure.
Is there any way to configure Radiator so that when it detects a very
slow database it stops using it (similar behaviour when the database
goes down, it backs off).
Authorization part is using .db files, so when the database is not
available authorization can continue. But when the database is slow, the
whole thins slows down to a point where the system is not usable.
Any comments, suggestions?
--
Igor Briski [EMAIL PROTECTED]
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
