we're running RadiusNT 2.5.175.0, and are having trouble with logging
accounting info to a SQL Server 7.0 database.
Everything runs happily for a day or so, then the logging to the Calls table
of the DB grinds to a halt. RadiusNT doesn't crash or log any error message,
but it stops logging, and it stops sending ACKs to the NASes.
If we restart the service, then everything comes back online, and we get a
flurry of records logged to Calls with big AcctDelayTimes. If we don't
restart the service then RadiusNT will remain in this hung state
indefinately. We've left it over a weekend before to see if it would timeout
or recover, with no luck.
We're fairly high usage, at peak times we get 7,000 records logged to the
Calls table an hour.
Has anyone else experienced anything simmilar? Is RadiusNT single-threaded,
so that if one INSERT to Calls hangs then the whole thing hangs?
Thanks for your help,
Ross McNab.
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart