Hello Matthew -
It sounds like your accounting table is much too large, causing SQL inserts to take a very long time. In general you should keep the accounting table as small as possible by archiving the older data. You should be able to see what is happening by looking at the database logs.
As you say, we will need to see a copy of the configuration file (no secrets) together with a trace 4 debug showing what is happening. But if it is an accounting insert that is taking a long time, it will be a database problem.
regards
Hugh
On Tuesday, Apr 1, 2003, at 04:10 Australia/Melbourne, Matthew Trout wrote:
We intended to use MySQL for both session databases, IP allocation and accounting; the former two seem to work fine, however as soon as we put accounting onto SQL the Accounting-Response packets take several seconds to be sent. The MySQL connections don't seem to be active during this time.
This was happening with and without Fork enabled, and the sending NASen were timing out, preventing users being authenticated.
Has anybody experienced anything similar? I know the information's patchy, but I don't have a spare install to test on currently - soon as I do I'll provide more complete info.
- Matt S Trout
Internet Systems Developer
Business Serve plc
NB: 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 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
