Accounting server terminates (when home-server is unavailable for a while)

Alan Buxey alan.buxey at gmail.com
Tue Nov 14 11:27:37 CET 2017


Accounting on port 1812, why? ;)

Send the output of gdb -

/app_log/radius/acct//gdb-acct-3088.log




On 14 Nov 2017 9:29 am, "Peter Balsianok" <balsianok.peter at gmail.com> wrote:

> Hi,
>
> I have problem with RADIUS server 3.0.15 (accounting). If home-server is
> unavailable, after while RADIUS servers terminates abnormally.
>
> proxy.conf (fragment):
> home_server sa_server_prod {
>   type = acct
>   ipaddr = 80.81.224.2
>   port = 1812
>   secret = "xxx"
>
>   # Without status check
>   status_check = none
> }
>
> home_server_pool prod_pool_sa {
>   home_server = sa_server_prod
> }
>
> realm sasro.sk {
>   nostrip
>   acct_pool = prod_pool_sa
> }
>
>
> Debug output:
> Tue Nov 14 10:22:18 2017 : ERROR: (1252) ERROR: Failing proxied request for
> user "56 at sasro.sk", due to lack of any response from home server
> 80.81.224.2 port 1812
> Tue Nov 14 10:22:18 2017 : ERROR: (1264) ERROR: Failing proxied request for
> user "169 at sasro.sk", due to lack of any response from home server
> 80.81.224.2 port 1812
> Tue Nov 14 10:22:26 2017 : ERROR: (1520) ERROR: Failing proxied request for
> user "g34 at sasro.sk", due to lack of any response from home server
> 80.81.224.2 port 1812
> Tue Nov 14 10:22:28 2017 : ERROR: (1577) ERROR: Failing proxied request for
> user "56 at sasro.sk", due to lack of any response from home server
> 80.81.224.2 port 1812
> Tue Nov 14 10:22:33 2017 : ERROR: (1703) ERROR: Failing proxied request for
> user "g34 at sasro.sk", due to lack of any response from home server
> 80.81.224.2 port 1812
> Tue Nov 14 10:22:38 2017 : Proxy: Marking home server 80.81.224.2 port 1812
> as dead.
> Tue Nov 14 10:22:39 2017 : ERROR: (1889) ERROR: Failing proxied request for
> user "169 at sasro.sk", due to lack of any response from home server
> 80.81.224.2 port 1812
> Tue Nov 14 10:22:40 2017 : Error: ASSERT FAILED src/main/process.c[3182]:
> request->home_server != NULL
> CAUGHT SIGNAL: Aborted
> Backtrace of last 7 frames:
> /app/radius/freeradius-3.0.15/lib/libfreeradius-radius.so(
> fr_fault+0x10c)[0x8a9166]
> /app/radius/freeradius-3.0.15/lib/libfreeradius-server.so(
> rad_assert_fail+0x49)[0xbdddfe]
> /app/radius/freeradius-v3/sbin/radiusd[0x8084145]
> /app/radius/freeradius-v3/sbin/radiusd[0x80808f3]
> /app/radius/freeradius-v3/sbin/radiusd[0x807c641]
> /lib/libpthread.so.0[0x50c912]
> /lib/libc.so.6(clone+0x5e)[0x81347e]
> Calling: gdb -silent -x /app/radius/conf/acct/panic.gdb
> /app/radius/freeradius-v3/sbin/radiusd 3088 2>&1 | tee
> /app_log/radius/acct//gdb-acct-3088.log
> Panic action exited with 0
> _EXIT(0) CALLED src/lib/debug.c[743]
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/
> list/users.html


More information about the Freeradius-Users mailing list