(RADIATOR) Re: Radiator issue

Hugh Irvine hugh at open.com.au
Fri Jul 29 02:49:36 CDT 2005


Hello Sergio -

The answer to your question depends entirely on how fast your SQL  
database is performing.

I am guessing that Radiator was waiting for the database inserts to  
occur.

You should have a look at a trace 4 debug from Radiator with a  
LogMicroseconds logger (requires Time-Hires from CPAN) to see how  
long each processing step is taking. A very good place to start  
improving performance is tuning the database and running two  
instances of Radiator - one for authentication and the other for  
accounting. This is very simple to do with a single configuration  
file, passing in the relevant parameters to radiusd on the command  
line. This has the great advantage of separating the authentication  
processing from the accounting processing, spreading the processing  
across both processors.

regards

Hugh


On 29 Jul 2005, at 17:12, Sergio Alejandro Gonzalez Z (S2010) wrote:

> Hello Hugh.
>
>
> I would like to know how many request per second a radiator
> instance would answer on a machine with the next
> characteristics:
>
> Sun V240 4 GB RAM 2 UltraSparc IIIi processors of 1.2 Ghz.
> Quad Gigabit Ethernet Card
>
> My question came up from a weird behavior I had yesterday
> on a machine with those specs that is handling about 150
> cisco RASes.
>
> Once the service was stalled (because the admin of such
> machine accidentaly filled up the / filesystem) and once it
> was cleaned, the radiator process was killed and ran it
> again. The machine was about 6.1 of uptime but the process
> of radiator was eating only about 7% of the cpu, and also
> mysqld (for accounting) was eating 40%.
>
> Many requests coming to the 1645 and/or 1646 ports was not
> responded, but when running another instance of radiator
> (using the same mysqld process) in another auth and acct
> ports, it worked well.
>
>
> Should be a reason the excesive amount of requests per
> secound the origin of such behavior?
>
>
> Once I guessed the non answering behavior was produced by
> the excesive requests coming from the RASes I restarted the
> server (init 6) but once it was up, once again the
> processes on the 1645 1646 ports didn`t work, and after
> killing the process and started again manually, everything
> went ok.
>
>
> What should I look for?. Any kernel tuning advice?.
>
>
> Thanks a lot in advance.
>
>
> Best regards
>
>
>
>
> Sergio Gonzalez
> IT Engineer.
>


NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/ 
radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.


--
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.


More information about the radiator mailing list