Hello everyone,
Last evening at about 9:00pm (which is prime time with many users
logging in) our primary radius server apparently started timing
out and requests were being passed along to our secondary radius
server (both are running Radiator 2.15).
In the radius.log of out backup radius server we started seeing
messages such as :
Mon Aug 21 21:01:02 2000: INFO: Access rejected for hma: No such
user
Our NASes (Ascend max) have a timeout of 40 seconds which seems
to be a long time and we would expect to rarely have requests
passed on to the secondary server. However, the timeout interval
was being reached.
As a corrective message we stopped/started radiusd on the
secondary server and this brought things back to normal, i.e.,
the "no such user" messages stopped.
Note that INFO messages did not appear in the log of the primary
server and we didn't have to reset radiusd on the primary server
nor were the NASes reset.
Has anyone experienced this type of behavior? What can be
occurring on our primary server to cause timeouts? And why were
we getting "no such user" messages?
Thanks in advance.
William Hern�ndez
radius.cfg
