On 11/27/2013 10:54 AM, Jakob Schlyter wrote: > I recently had a case where Radiator was restarted while the upstream RADSEC > host was down (or at least not connecting successfully), resulting in the > server logging excessively every second or so until the disk was full... > > Wed Nov 20 23:59:59 2013: INFO: AuthRADSEC could not find a working host to > forward to. Ignoring > Wed Nov 20 23:59:59 2013: INFO: AuthRADSEC: No reply from XXX:2083 for XXX" > (53) > > Is there any way to have <AuthBy RADSEC> to simply give up after some time?
Hello Jakob, can you reply with your Radiator configuration (no secrets or passwords required) and tell what is the Radiator version. Thanks, Heikki -- Heikki Vatiainen <[email protected]> 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 etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator
