(RADIATOR) Multiple Servers, centralised logging

[John Coy]

Dave,

The system you're describing does have a weakness in file-locking and a 
potential for data to be lost.  If both Radius servers attempt to log at 
the same time, one set of data will be overwritten by the other.  On a busy 
system, this could happen more often than you'd think.

The most efficient way to use two servers and centralized logging is by 
setting up a database server to accept logging.  There is good support for 
this in Radiator -- reference the manual for more information.  

An added advantage of setting up a Database server for logging is you could 
also set it up for authentication -- once you do that, you have a 
centralized place for updates as well.  

We use a single database server and export the authentication data to flat 
text files for backup in case the database server fails.

Hope that helps.

> Hi All,
> 
> We're currently using 2 RADIUS servers, basically a primary and a
> secondary in case the primary isn't available. Both servers  share a
> mounted file system to write logfiles to, so that when I run radwho or
> radacct I get information from both servers at a glance. I'm concerned
> that sooner or later I'm going to come across a race condition and have
> problems. Is there a better way of doing this, or is this method
> totally "safe"?
> 
> Thanks,
> 
> Dave Walters
> Technical Manager
> Luna Internet
> Tel. 01782 544 099
> Fax. 01782 535 184
> Mob. 07968 729 489
> dave at lunainternet.net
> www.luna.co.uk
> 
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.


===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.