Someone on the list can correct me if I'm wrong. But I always thought this message meant that the radius server didn't respond as fast as the NAS had expected, so, the NAS re-sent the request. Then the radius server ended up with 2 identical requests. Its discarding the one, and acting upon the other. Now this delayed response by the radius server could very well be caused by trouble with your backend db, hardware, or whatever. I see this message on occasion, as I have a VERY high traffic radius server. 8 to 10 requests per second at peak hours. It never causes my radius server to stop working completely, and none of my end users even see a problem because the radius server acts appropriately with the new request. Chris Carver Pennswoods.Net Network Engineer Quoting Andrew Grimmett <agrimmett@lssi.net>:
Sat May 13 07:14:53 2006 : Error: Discarding new request from client remotehost:1 027 - ID: 17 due to live request 112
I received the above error this morning, after the event no additional requests were processed or events logged through radius. I stop and started the radius server and requests started working again. I checked the mail-archive and found a couple of references to this, backend not responding and cpu load. I checked the backend (ldap) and seen that it was processing requests ok from other devices. Any ideas of were the problem occurred or where I can find more info on this error?
Thanks for your help, Andrew - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html