Hi,
Instead of writing accounting data directly to the MySQL db, we configured it to write the sql statements to the sql-relay file and set a crontab to dump it to the remote db every 15 minutes using *radsqlrelay* command:
radsqlrelay -x -h x.x.x.x -d mysql -b mysqldb -u root -pdbpassword -1 /var/log/radius/radacct/sql-relay
ummmm. urgh. use the buffered-sql virtual server to do this natively.
We start doing investigations and found that in the radius.log there are many errors happening in the same time the radsqlrelay running by the crontab, the error is below:
the server is trying to do lots of DB connections...and you dont have many connections defined (and also not many spares) - open up a great deal more connections to your SQL.... *then* start looking at SQL performance to ensure that any possible bottlenecks you can remove ARE removed (eg nice InnoDB instead of MyISAM, nice use of indexes on the data. clear out old accounting data etc. ...and there are bugs/issues - thats why there have been 7 releases since your version - 3.0.11 is the current 3.0.x release :-) alan