On Monday 17 Oct 2011 14:49:33 Arran Cudbard-Bell wrote:
Procedure to reproduce the bug ? :)
If I fire anything off to the upstream eduroam proxies, it either just fails or segfaults, normally fails on the first try, then segfaults when I re-try. Marking home server 194.82.174.185 port 1812 as zombie (it looks like it is dead). PING: Zombie period is over for home server jrs0 Marking home server 194.82.174.185 port 1812 as dead. PING: Already pinging home server jrs0 PING: Waiting 4 seconds for response to ping Sending Status-Server of id 136 to 194.82.174.185 port 1812 Message-Authenticator := 0x00 NAS-Identifier := "Status Check 0. Are you alive?" PING: Next status packet in 30 seconds Waking up in 3.9 seconds. rad_recv: Access-Request packet from host 10.0.2.52 port 32769, id=4, length=206 (2) Failed to insert entry into proxy list. (2) Failed to insert initial packet into the proxy list. No Post-Proxy-Type Fail: ignoring Waking up in 2.8 seconds. rad_recv: Access-Request packet from host 10.0.2.52 port 32769, id=4, length=206 Segmentation fault Program received signal SIGSEGV, Segmentation fault. 0x000000000042a6f4 in request_proxied (request=0x87f720, action=3) at process.c:2691 2691 if ((home->state == HOME_STATE_IS_DEAD) || (gdb) bt #0 0x000000000042a6f4 in request_proxied (request=0x87f720, action=3) at process.c:2691 #1 0x000000000042e65b in request_receive (listener=0x871d30, packet=0x883e40, client=0x822890, fun=0x40b5f0 <rad_authenticate>) at process.c:1245 #2 0x0000000000419746 in auth_socket_recv (listener=0x871d30) at listen.c:1359 #3 0x0000000000429348 in event_socket_handler (xel=<value optimized out>, fd=0, ctx=0x1c) at process.c:3269 #4 0x00002aaaaaad6854 in fr_event_loop (el=0x85c3d0) at event.c:415 #5 0x00000000004203de in main (argc=<value optimized out>, argv=<value optimized out>) at radiusd.c:424 The home server isn't dead, but when using 3.0.0 it always says it's dead :( Regards -- Steven Coutts stevec@couttsnet.com