detail server stopped working silently

adrian.p.smith at bt.com adrian.p.smith at bt.com
Fri Oct 24 17:36:47 CEST 2014


>  As I've said, there are fixes in the v3.0.x branch in git.  Please try that.
>  https://github.com/FreeRADIUS/freeradius-server/
>  And grab the v3.0.x branch.  Build it.  Install it.  Test it.  Please.

Hi Alan,

We have made some more progress today. We have tried using the v3.0.x branch and got similar results which led us to try further tests.

Because we see the debug output saying the remote server has stopped responding we tried sending the detail file packets back to our self on the local machine. This was a total success. Then suspecting that the network between the machines was a contributing factor, we tried another "closer" machine on the same subnet and this was also successful.

Reverting back to the original remote machine shows the problem still exists on both 3.0.3 and v3.0.x and hopefully the debug extract below shows what happens. Once the Status-Server message has been answered the detail processing on the sending server never re-starts even though the remote server is marked as alive. The detail.work remains in the radacct folder and any new files appearing there are also ignored. It feels like even if a remote server or network is slow or un-reliable, Freeradius should be able to recover and continue processing the detail file.

Waking up in 4.3 seconds.
(1014) No proxy response, giving up on request and marking it done
Marking home server 192.168.49.10 port 1813 as zombie (it has not responded in 20 seconds).
PING: Waiting 4 seconds for response to ping
Sending Status-Server Id 146 from 0.0.0.0:53177 to 192.168.49.10:1813
        Message-Authenticator := 0x00
        NAS-Identifier := 'Status Check 0. Are you alive?'
PING: Next status packet in 30 seconds
(1014) ERROR: Failing request - proxy ID 62, due to lack of any response from home server 192.168.49.10 port 1813
(1014) Cleaning up request packet ID 246 with timestamp +12
Waking up in 0.2 seconds.
Received Accounting-Response Id 146 from 192.168.49.10:1813 to 192.168.19.20:53177 length 20
(1016) Received response to status check 1016 (1 in current sequence)
(1016) Marking home server 192.168.49.10 port 1813 alive
Waking up in 0.2 seconds.
(1015) Cleaning up request packet ID 55 with timestamp +27
Ready to process requests.

Any more help appreciated.

Regards,

Adrian



More information about the Freeradius-Users mailing list