Hello Chris -
On Thu, 31 Aug 2000, Chris M wrote:
> When I first used radacct on 2.16.1 things seemed to work great.
>
> Then I imported a whole bunch of call data to the MySQL database. The
> database is about 1.4Gig in size now.
>
> When I run radacct.cgi I watch the raw Radiator logs and see that it is
> getting a SQL Timeout. If I watch top -d I see that mysql is churning away
> burning up the CPU.
>
> So it appears that for some reason SQL authentications are getting held off
> and are actually timing out while the radacct.cgi query is running.
> Actually, I authenticate from the shadow password file, the AuthSQL is
> basically only used for accounting purposes.
>
> Any ideas on what the issue could be?
>
There are a couple of issues here. The first is the size of the database - do
you really need to keep all of that data online? If so, you should have a look
at your indexes to see if you can speed things up. Secondly, if you have
problems with the accounting processing, you should set up two copies of
Radiator, one listening on the authentication port and the other listening on
the accounting port. This will let the authentications be processed
independently of the accounting. You would do something like this:
# authentication only copy of Radiator
AuthPort 1645
AcctPort
.......
# accounting only copy of Radiator
AuthPort
AcctPort 1646
......
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
