radius configuration suggestions

[Szymon Roczniak]

On Sun, Sep 06, 2009 at 02:39:34PM +0530, ramesh p wrote:
>    when one radius server packets are writing/updating other server packets
>    are locked and waiting for mysql. This i observed using show full
>    processlist. We are using default storage engine MyISAM. And the writes

Try switching it to InnoDB instead, at least on the server where you collect
all your data. Get rid of all indexes that you would only use for SELECTs,
keep only those needed for your update query. Also make sure that no other
queries run on this box (no selects) - create a slave box and do all your
selects on the slave. You can have MyISAM tables on the slave and all
additional indexes you need to speed up reads. As a bonus, you can also do
backups on the slave without affecting your master DB and the radius servers.

If this doesn't help you can make your radius boxes log to a local file
instead of writing directly to the database and then use radsqlrelay script to
do all the writes. 

>    are through network i mean sql in different server instead of radius
>    server. Radius process also crashing due mysql db handles not available,
>    no socket to handle requests.

Maybe the only thing that needs tuning is the num_sql_socks option in your sql
module to match the number of radius servers (max_servers in radiusd.conf)?

-- 
szymon roczniak
simon at dischaos.com