I've had similar problems with other AAA-related logging systems where it was important to have the records, but not necessarily immediately. My solution was to sent the accounting data to another more easily supportable resource, like syslog, and then use a system like syslog-ng to aggregate it all to the db server and run a shell/perl script periodically to import the records to the db. You loose a little bit of speed, but if raw speed isn't that important, it's more easily supportable and depending on you systems, possibly more robust. Thanks. Dan On Mon, 2007-01-22 at 10:41 -0500, Dourty, Brian R. (IATS) wrote:
We have configured our radius servers to send accounting information to an Oracle database. It works our really well except when the oraclce database server isn’t available (I.E. maintenance or cold backups). The radius process dies when it loses connectivity to the oracle server. Has anyone else noticed this problem? Any suggestions on how to make radiusd more robust and able to recover from this?
Thanks,
Brian Dourty
System Administrator - Team Lead
IAT Services
University of Missouri - Columbia
573-882-1035
plain text document attachment (ATT5655462.txt), "ATT5655462.txt" - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- Dan Geist | dan.geist@cox.com | (404) 269-6822 Cox Communications - Engineering Security