I'm sure I read about this issue on the list around the release of 3.0.27/3.0.5 and had thought it was fixed but searching for it in the list archive isn't coming up with anything recent. This one is running 3.0.27 - the server is segfaulting when it tries to probe a remote radius server that is unreachable: No response to status check 5 ID 75 for home server 193.63.195.50 port 1812 bt full follows at the end of the email. I do have plans to upgrade to 3.2 but not before I'd like this particular system in production. Is this a known/previously seen issue, or am I inventing a memory? Many Thanks, Adam --- #0 0x0000555555587244 in request_stats_final (request=0x555555a69bb0) at src/main/stats.c:99 listener = <optimized out> client = <optimized out> auth_stats = <optimized out> coa_stats = <optimized out> #1 0x000055555558f811 in request_stats_final (request=0x555555a69bb0) at src/main/stats.c:91 listener = <optimized out> client = <optimized out> auth_stats = <optimized out> coa_stats = <optimized out> dsc_stats = <optimized out> done = <optimized out> proxy_stats = <optimized out> #2 request_done (request=0x555555a69bb0, original=<optimized out>) at src/main/process.c:921 now = {tv_sec = 93824996240744, tv_usec = -7131984328893351168} when = {tv_sec = 140737488347520, tv_usec = 1} action = <optimized out> #3 0x0000555555591b73 in request_ping (request=0x555555a69bb0, action=<optimized out>) at src/main/process.c:3788 home = <optimized out> buffer = "193.63.195.50\000\000\000 x\246UUU\000\000\000\000\000\000\000\000\000\000x\330\363\367\377\177\000\000\024\206\345\367\377\177\000\000\020\020\246UUU\000\000\060\000\000\000\000\000\000\000\310n\222UUU\000\000X\234\246UUU\000\000Pm\222UUU\000\000\001\000\000\000\000\000\000\000\020\020\246UUU\000\000\t\244\345\367\377\177\000\000Y4[UUU\000\000B4[UUU\000" __FUNCTION__ = "request_ping" #4 0x00007ffff7f33abb in fr_event_run (when=0x7fffffffe180, el=0x555555926d50) at src/lib/event.c:321 callback = 0x555555587a80 <request_timer> ctx = 0x555555a69bb0 ev = <optimized out> callback = <optimized out> ctx = <optimized out> ev = <optimized out> #5 fr_event_run (el=el@entry=0x555555926d50, when=when@entry=0x7fffffffe180) at src/lib/event.c:278 callback = <optimized out> ctx = <optimized out> ev = <optimized out> #6 0x00007ffff7f36c3f in fr_event_loop (el=0x555555926d50) at src/lib/event.c:691 i = <optimized out> rcode = 0 when = {tv_sec = 1730907338, tv_usec = 458268} wake = <optimized out> read_fds = {fds_bits = {0 <repeats 16 times>}} write_fds = {fds_bits = {0 <repeats 16 times>}} #7 0x000055555556c3cc in main (argc=<optimized out>, argv=<optimized out>) at src/main/radiusd.c:641 rcode = 0 status = <optimized out> argval = <optimized out> spawn_flag = true display_version = false flag = 0 from_child = {-1, -1} p = <optimized out> state = <optimized out> autofree = 0x5555555d8620 Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under company number. 05747339, VAT number GB 197 0632 86. Jisc’s registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800. Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 02881024, VAT number GB 197 0632 86. The registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800. Jisc Commercial Limited is a wholly owned Jisc subsidiary and a company limited by shares which is registered in England under company number 09316933, VAT number GB 197 0632 86. The registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800. For more details on how Jisc handles your data see our privacy notice here: https://www.jisc.ac.uk/website/privacy-notice