Question regarding retrying of requests in detail-combined file
Hi all :) FreeRADIUS 2.1.7 CentOS 5.2 I am not too sure where to start here so I will describe the symptoms first: I have 2 freeradius servers that both receive accounting requests, and proxy these requests to each other, as well as log these requests to a detail file. I have noticed now that while server A is processing the detail-combined file and proxying the requests to server B, server B will fail to get a lock on its detail file, and the request will fail. When this happens it is not passing anything back to server A, and server A does not seem to be timing out the request, so it stops processing the detail-combined file and just sits there. A bit more in depth, server B is still running FR 1.1.6. I am in the process of updating to 2.1.7 but am being delayed due to outdated OS, so am moving this lot to a new server. The lock fail is occurring when server B tries to get a lock on the detail-combined file, so it is very likely that I have had the proxying setup incorrectly here all along, but since it is 1.1.6 I do not expect help here... What I would like to try figure out is how to get server A (2.1.7) to time out a proxy request and retry it... Any pointers to sections/docs would be great as always, Thanks a mill! Patric
Add this line to the home server configuration of Server A (running 2.1.7): no_response_fail = yes Tim
-----Original Message----- From: freeradius-users- bounces+tim.sylvester=networkradius.com@lists.freeradius.org [mailto:freeradius-users- bounces+tim.sylvester=networkradius.com@lists.freeradius.org] On Behalf Of Patric Sent: Thursday, October 15, 2009 12:05 AM To: FreeRadius users mailing list Subject: Question regarding retrying of requests in detail-combined file
Hi all :)
FreeRADIUS 2.1.7 CentOS 5.2
I am not too sure where to start here so I will describe the symptoms first:
I have 2 freeradius servers that both receive accounting requests, and proxy these requests to each other, as well as log these requests to a detail file. I have noticed now that while server A is processing the detail- combined file and proxying the requests to server B, server B will fail to get a lock on its detail file, and the request will fail. When this happens it is not passing anything back to server A, and server A does not seem to be timing out the request, so it stops processing the detail-combined file and just sits there.
A bit more in depth, server B is still running FR 1.1.6. I am in the process of updating to 2.1.7 but am being delayed due to outdated OS, so am moving this lot to a new server. The lock fail is occurring when server B tries to get a lock on the detail-combined file, so it is very likely that I have had the proxying setup incorrectly here all along, but since it is 1.1.6 I do not expect help here...
What I would like to try figure out is how to get server A (2.1.7) to time out a proxy request and retry it...
Any pointers to sections/docs would be great as always,
Thanks a mill! Patric
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Tim Sylvester wrote:
Add this line to the home server configuration of Server A (running 2.1.7):
no_response_fail = yes
Hi Tim, That worked perfectly! Thank you :) Rejecting request 191 (proxy Id 218) due to lack of any response from home server xxx.xxx.xxx.xxx port 1813 No response configured for request 191. Will retry in 30 seconds Finished request 191. Cleaning up request 191 ID 56389 with timestamp +140 PROXY: Marking home server xxx.xxx.xxx.xxx port 1813 as zombie (it looks like it is dead). Sending Status-Server of id 46 to xxx.xxx.xxx.xxx port 1813 Message-Authenticator := 0x00000000000000000000000000000000 NAS-Identifier := "Status Check. Are you alive?" Waking up in 0.8 seconds. Waking up in 3.9 seconds. rad_recv: Access-Accept packet from host xxx.xxx.xxx.xxx port 1813, id=46, length=49 And 30 seconds later the request is retried and succeeds :) Is there any way for me to decrease the retry delay? In my specific case I know why its failing so retrying sooner should not be a problem. Also, since both servers are mine, I have setup my virtual server with the following parameters. Any suggestions or tweaks would be appreciated :) home_server copy-acct-to-server-b { type = acct ipaddr = xxx.xxx.xxx.xxx port = 1813 secret = my_secret response_window = 10 zombie_period = 20 #revive_interval = 120 (read in the docs that use of this is not recommended?) status_check = status-server check_interval = 10 num_answers_to_alive = 1 no_response_fail = yes } Thanks again! Patric
Alan DeKok wrote:
Patric wrote:
And 30 seconds later the request is retried and succeeds :) Is there any way for me to decrease the retry delay?
See the "retry_interval" configuration in the detail listener.
Hi Alan, Would I be correct in my understanding that I add that here: sites-enabled/copy-acct-to-home-server: ----------------------------------------- server copy-acct-to-home-server { listen { type = detail filename = ${radacctdir}/detail-combined load_factor = 10 retry_interval = 10 <----------------- } } Thank you :) Patric
participants (3)
-
Alan DeKok -
Patric -
Tim Sylvester