Roy Kartadinata wrote: > We currently use version 1.1.4 with SQL support for both authentication > and accounting.
Upgrade.... > What happened yesterday was both remote servers went down for 3 hours > and during that time our log was bombarded by the following error: > > Proxy: No outstanding request was found for proxy reply from home server > 192.168.12.175:1813 - ID 111 Hmm... that usually happens when the home server comes back *up*, but too late for the proxying server to handle the request. > To my understanding, freeradius should mark that remote server as a dead > host but we are still receiving the error above even though we do have > the same accounting record in our SQL database. We even tried to disable > proxy to no luck, the same error were still showing in our log file like > radiusd queuing the requests some how. Has anyone seen this before? Nope. It's 1.1.4. Upgrade. The latest versions are infinitely better. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
