Hello Roberto -
This is almost always a problem with the backend authentication resource.
A trace 4 debug with LogMicroseconds (requires Time::HiRes from CPAN) will show
you how long each processing step is taking.
What I generally see is Radiator waiting for an external resource and at some
critical number of requests per second the UDP queue starts to fill up leading
to timeouts and retransmissions.
Ie. if the external resource takes say 50 ms to respond, then it follows that
at most you can process 20 requests per second - anything over that will lead
to the problem I describe.
This is just one theory, but as I say, a trace 4 debug with LogMicroseconds
will tell you where to look.
regards
Hugh
> On 25 Aug 2015, at 03:41, Ullfig, Roberto Alfredo wrote:
>
> Hello all,
>
>
>
> It’s the first day of classes here and we’re seeing hourly successful
> authentication-count downward spikes starting around 5-10 minutes before the
> hour – was wondering if any other people here see the same thing in their
> environments and
>
>
>
> We’re looking at the number of successful authentications per 5 minutes.
> During the summer we would max out at 5K but there were no downward spikes.
> We are now hitting 30K (shortly before noon) and this span of perhaps 20
> minutes.
>
>
>
> ---
>
> Roberto Ullfig – rull...@uic.edu
>
> ACCC Research Programmer
>
>
>
> ___
> radiator mailing list
> radiator@open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
--
Hugh Irvine
h...@open.com.au
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER, SIM, etc.
Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc.
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
