> What's *probably* happening is that the SQL server is taking a long > time to respond. So every radius request takes 3-4 second longer than > normal, due to SQL. If you get 100's of requests per second, then you > will run out of sockets quickly. >
You're right, the server take a long time to respond ! And even with only 2 or 3 radius request per second, the SQL server can't answer to radius needs ! > Have you indexed your SQL tables? How long does it take to do the > queries when you run in debug mode, and send it test packets? In debug mode, it can take up to 8 second to answer. This happen because i do a lot of extraction on the SQL server. To solve the problem, I install another SQL server with SQL replication to the server where i do a lot of SQL query. Now freeradius-snapshot-20020215 doesn't complaint with socket :o) Freeradius is the best free radius server. Thanks everybody for your help - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
