[RE]Problem with proxied accounting

[Ivan Kalik]

> We have just upgraded to FreeRADIUS 2.1.6, but unfortunately the problem
> persists:
>
>
>
> Server1/:
> total 1008236
> -rw-------  1 root root 714751062 Jul 29 11:53 detail-20090729
> -rw-------  1 root root 316653344 Jul 29 07:29 detail.work <= stuck!
>
>
> We got sometimes the following message for Server2:
>
> Thu Jul 23 15:00:45 2009 : Proxy: No outstanding request was found for
> proxy reply from home server <Server2 IP address> port 1813 - ID 142
> And several messages for Server1:
>
> Wed Jul 29 11:36:53 2009 : Error: Rejecting request 3993531 due to lack of
> any response from home server <Server1 IP address> port 1813
> Wed Jul 29 11:36:53 2009 : Error: PROXY: Marking home server <Server1 IP
> address> port 1813 as zombie (it looks like it is dead).
> Wed Jul 29 11:37:28 2009 : Info: Suspicious proxy state... continuing
> Wed Jul 29 11:37:30 2009 : Error: Rejecting request 3998634 due to lack of
> any response from home server <Server1 IP address> port 1813
> <...>
>
>
>
> In an attempt to force the revival of Server1, we scheduled the execution
> of the following command every minute:
>
> radmin -e "set home_server state <Server1 IP address> 1813 alive"
>

Ugh, don't do that.

>
>
> But still, it seems to stuck ... I checked with "tcpdump port 1813 and
> host <Server1 IP address>" that even though the details.work for Server1
> is freezed, FreeRADIUS is sending accounting requests to Server1 and it is
> receiving accounting responses.
>
>
>
> # tcpdump port 1813 and host <Server1 IP address>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
> 11:39:27.667255 IP <FreeRADIUS IP address>.1814 > Server1.radius-acct:
> RADIUS, Accounting Request (4), id: 0x0c length: 202
> 11:39:27.675969 IP Server1.radius-acct > <FreeRADIUS IP address>.1814:
> RADIUS, Accounting Response (5), id: 0x0c length: 20
> <...>

Is there a firewall blocking requests? Server1 is sending responses but
they are not reaching the proxy.

Ivan Kalik
Kalik Informatika ISP