Hello Mahmoud -
The debug you posted shows that Radiator is responding to the Access-Request
with an Access-Accept, but 5 seconds later a duplicate Access-Request is
processed and the same Access-Accept is returned.
I think you will need to check a debug on your client device to see what is
Either the Access-Accept is not getting back to the client device, or it is
getting there after the client device has timed out and resent (ie. 5 second
This sort of behaviour can also be caused by Radiator having to wait for
something like SQL database access, but there isn’t enough information in your
debugs to be able to say if this is the case.
> On 19 Feb 2017, at 19:25, Mahmoud Abdelsalam <m.abdelsa...@wimd.com.kw> wrote:
> Radiator recently reports a lot of duplicates:
> the real problem is sometimes Radiator times out during peak time with the
> below error and I have to restart radiator to clear it:
> radclient: no response from server for ID 46 socket 3
> Here is trace4 for the auth request I made locally:
> Also here is my Access configurations:
> Kindly advise.
> Best Regards,
> Mahmoud Abdelsalam.
> radiator mailing list
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