Hi everybody, We currently use version 1.1.4 with SQL support for both authentication and accounting. We also have proxy setting that sends accounting record to a remote server but keep the authentication local using the following setup: retry_delay = 10 retry_count = 5 dead_time = 120 default_fallback = yes realm 1x.domain.com { type = radius authhost = LOCAL accthost = 192.168.12.175:1813 secret = xxxxxx } realm 1x.domain.com { type = radius authhost = LOCAL accthost = 192.168.12.178:1813 secret = xxxxxx } 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 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? Cheers, Roy
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.
Thanks, I guess my only option is to upgrade .. :) Cheers, Roy -----Original Message----- From: freeradius-users-bounces+rkartadinata=pocket.com@lists.freeradius.org [mailto:freeradius-users-bounces+rkartadinata=pocket.com@lists.freeradiu s.org] On Behalf Of Alan DeKok Sent: Tuesday, June 17, 2008 10:22 AM To: FreeRadius users mailing list Subject: Re: Proxy behavior 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
participants (2)
-
Alan DeKok -
Roy Kartadinata