The original message was received at Thu, 15 Oct 1998 02:18:44 -0400 (EDT)
from ns.gte.com [18.104.22.168]
----- The following addresses had permanent fatal errors -----
(expanded from: <email@example.com>)
----- Transcript of session follows -----
firstname.lastname@example.org... Deferred: Connection timed out with sigint.gte.com.
Message could not be delivered for 5 days
Message will be deleted from queue
Reporting-MTA: dns; newman.gte.com
Arrival-Date: Thu, 15 Oct 1998 02:18:44 -0400 (EDT)
Final-Recipient: RFC822; <email@example.com>
X-Actual-Recipient: RFC822; firstname.lastname@example.org
Remote-MTA: DNS; sigint.gte.com
Last-Attempt-Date: Tue, 20 Oct 1998 02:32:53 -0400 (EDT)
Received: from ns.gte.com (ns.gte.com [22.214.171.124])
by newman.gte.com (8.9.1/8.9.1) with ESMTP id CAA26518
for <email@example.com> Thu, 15 Oct 1998 02:18:44 -0400 (EDT)
Received: from relay.gte.com by ns.gte.com (8.7.5/)
Received: (from postman@localhost) by relay.gte.com (8.7.5/8.7.5) id CAA21868 for <firstname.lastname@example.org> Thu, 15 Oct 1998 02:18:42 -0400 (EDT)
Received: from unknown(126.96.36.199) by relay.gte.com via smap (V1.3)
id sma021860; Thu Oct 15 02:18:29 1998
Received: from walnut.iea-software.com (walnut.iea-software.com [188.8.131.52]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za002321 for <radiusNT@iea-software.com> Wed, 14 Oct 1998 22:43:09 -0700
Received: from [184.108.40.206] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id hvkbaaaa for <radiusNT@iea-software.com> Wed, 14 Oct 1998 22:43:05 -0700
Date: Wed, 14 Oct 1998 22:56:13 -0700
From: "Dale E. Reed Jr." <email@example.com>
Organization: IEA Software, Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; I)
Subject: Re: RadiusNT slow to Autenticate with Sequel
Content-Type: text/plain; charset=us-ascii
X-Info: -Reply-To: firstname.lastname@example.org
X-ListMember: email@example.com [radiusNT@iea-software.com]
> RadiusNT 2.2 Running as a service
> Two Radius Servers one Sequel Server
> Radius servers both Pentium 166, 128mb ram, SCSI HD
> Sequel server Dual Pentium 200, 196mb ram, 4 gig SCSI HD, Adaptec 2940
> NAS Ascend Max 4000's (14) Have tried 5.x and 6.x code
> Sequel server 6.5 300mb for database, 30mb temp db
> Running only authentication (no accounting) Radius will run and verify ok
> but radius response times show to range from 1600ms to 4000ms. No other
> debug errors.
Realize two things. First, running in foreground debug mode will slow
RadiusNT down by a factor of 10 soley because of screen refresh issues.
If you minimize the window, make a request, and restore it, you'll see
what I am talking about (versus leaving it open). Secondly, the
of RadiusNT is directly related to the configuration of your SQL Server
and the design of the database. For example, indexes, proper
and proper configuration can make a database perform countless times
than a system that isn't properly setup. It only gets worse as your DB
grows if this isn't setup right.
The SQL Server scripts included with RadiusNT are not fully optimized.
They are designed as a base to start from to create your own database
from. For example, the login field is indexed, but I don't see one
for the shell and Email fields, which are equally as important for
authentication (the email is an addition in 2.5, whereas that script
was originally written for 2.2).
> Then at some random interval (a day or a week) the Sequel server processor
> usage will skyrocket and authentications will fail. Debug shows no errors
> but it seems as if the NAS is sending many repeated requests that can't be
> processed. User names will be repeated from one or more Max's. Opening the
> Max profile, leaving the authentication servers set, will result in the
> Sequel server dropping back to normal after a period (20-30min). The Max's
> can be the reset to use the radius profile again and may run for another few
> days or weeks.
This could be some issues with the calls table. RadiusNT 2.2 used the
DSN for auth and accounting. By delting records from the calls table (a
of the maintenance I mentioned above) the calls table will be locked.
2.2, that stopped everything, including authentication (it would timeout
after 30 seconds, but would basically be dead). RadiusNT 2.5 solved
problem by using two DSNs and two threads (1 each for Auth and
This easilt doubles the performance of RadiusNT alone. I would highly
recommend looking at RadiusNT 2.5.
> There seems to be no ryme or reason why this happens it will happen during
> high and low auth periods. This only thing that seems to show is the
> 1800-4000ms times for radius which I thought would be a lot quicker.
Typical RadiusNT auth times should be ~300ms max. Anything more needs
> Any Ideas why this might happen, where to look or what can be tweaked with
> Sequel for a preformace boost. We have been trying to work this out for a
> couple of months.
Two things I would do is run a checkdb to make sure the DB is in order
and also update your statistics/indexes. The laster is vital when you
change a lot of data in your database, since the index may be out of
date and therefore causing SQL Server to do a full table scan (which
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com