FreeRADIUS fails when home server is marked as dead

[Alan DeKok]

On Aug 7, 2018, at 10:08 AM, matt.southward at gmail.com wrote:
> 
> I am proxying accounting to a 3rd party. This works fine until the 3rd
> party stops sending accounting responses. The following is logged when this
> occurs:
> 
> Mon Aug  6 17:38:28 2018 : Proxy: Marking home server xxx.xxx.xxx.xxx port
> 1813 as zombie (it has not responded in 30.000000 seconds).
> 
> Mon Aug  6 17:38:28 2018 : ERROR: (29383) ERROR: Failing proxied request,
> due to lack of any response from home server xxx.xxx.xxx.xxx port 1813
> 
> Mon Aug  6 17:38:58 2018 : Proxy: Marking home server xxx.xxx.xxx.xxx port
> 1813 as dead.
> 
> Mon Aug  6 17:38:58 2018 : Info: SOFT ASSERT FAILED src/lib/event.c[161]:
> *(ev->parent) == ev

  Upgrade to 3.0.17.

> Mon Aug  6 17:38:58 2018 : Info: SOFT ASSERT FAILED src/lib/event.c[167]:
> ret == 1
> 
> 
> At this point the server stops responding to everything, including access
> requests.

  Because it's down.

> 
> I don't care if I get a response back from this server as I'm also storing
> accounting data locally in an SQL database. How do I configure FreeRADIUS
> to continue working even if the server I'm proxying accounting to doesn't
> respond.

  Use a recent version of the server.

> My apologies ahead of time as I'm betting this is somewhere in the
> documentation...I'm just not seeing it or not understanding what I'm
> reading.

  Crashes aren't documented.  Just upgrade to the latest release, and 99.99% of the time they'll be fixed.

  Alan DeKok.