Thanks Alan, It was working fine, then I saw a messgage in log as below: According to the log home server is dead but I checked the server 10.128.5.1 and it is working. There has been nothing change in the NAS ( at least net guys told me). Since the message below freeradius1 server stopped authenticating users. ntlm_auth, eap_pol test works okay as usual. I even tried stopping primary radius server for a while to see freeradius1 will start processing user authentication - but it doesn't ! This is the version I am using now .freeradius-2.1.12-6.el6.x86_64 Any hint or guide would help me. Oct 20 10:20:01 freeradius1 radiusd[1387]: Marking home server 10.128.5.1 port 1812 as zombie (it looks like it is dead). Oct 20 10:20:01 freeradius1 radiusd[1387]: Received response to status check 221055 (1 in current sequence) Oct 20 10:20:02 freeradius1 radiusd[1387]: Internal sanity check failed for child state Oct 20 10:20:02 freeradius1 radiusd[1387]: Reply from home server 10.128.5.1 port 1812 - ID: 119 arrived too late for request 220456. Try increasing 'retry_d elay' or 'max_request_time' Oct 20 10:20:21 freeradius1 radiusd[1387]: Marking home server 10.128.5.1 port 1812 as zombie (it looks like it is dead). Oct 20 10:20:22 freeradius1 radiusd[1387]: Internal sanity check failed for child state Oct 20 10:20:22 freeradius1 radiusd[1387]: Reply from home server 10.128.5.1 port 1812 - ID: 157 arrived too late for request 220836. Try increasing 'retry_d elay' or 'max_request_time' Oct 20 10:20:22 freeradius1 radiusd[1387]: Received response to status check 221132 (1 in current sequence) Oct 20 10:20:23 freeradius1 radiusd[1387]: ... adding new socket command file /var/run/radiusd/radiusd.sock Oct 20 10:20:23 freeradius1 radiusd[1387]: ... closing socket command file /var/run/radiusd/radiusd.sock Oct 20 10:20:27 freeradius1 radiusd[1387]: ... adding new socket command file /var/run/radiusd/radiusd.sock Oct 20 10:20:27 freeradius1 radiusd[1387]: ... closing socket command file /var/run/radiusd/radiusd.sock Oct 20 10:20:55 freeradius1 radiusd[1387]: Rejecting request 221141 (proxy Id 199) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:20:55 freeradius1 radiusd[1387]: Marking home server 10.128.5.1 port 1813 as zombie (it looks like it is dead). Oct 20 10:20:55 freeradius1 radiusd[1387]: Received response to status check 221267 (1 in current sequence) Oct 20 10:20:56 freeradius1 radiusd[1387]: Marking home server 10.128.5.1 port 1813 as dead. Oct 20 10:20:56 freeradius1 radiusd[1387]: Rejecting request 221145 (proxy Id 172) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:20:58 freeradius1 radiusd[1387]: Rejecting request 221155 (proxy Id 193) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:01 freeradius1 radiusd[1387]: Rejecting request 221163 (proxy Id 64) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:01 freeradius1 radiusd[1387]: Rejecting request 221166 (proxy Id 99) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:04 freeradius1 radiusd[1387]: Rejecting request 221180 (proxy Id 161) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:06 freeradius1 radiusd[1387]: Rejecting request 221191 (proxy Id 250) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:07 freeradius1 radiusd[1387]: Rejecting request 221193 (proxy Id 192) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:09 freeradius1 radiusd[1387]: Rejecting request 221207 (proxy Id 159) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:12 freeradius1 radiusd[1387]: Rejecting request 221221 (proxy Id 212) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:12 freeradius1 radiusd[1387]: Rejecting request 221224 (proxy Id 25) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:14 freeradius1 radiusd[1387]: Rejecting request 221233 (proxy Id 131) due to lack of any response from home server 10.128.5.1 port 1813 Oct 20 10:21:26 freeradius1 radiusd[1387]: No outstanding request was found for reply from host 10.128.5.1 port 1813 - ID 172 Oct 20 10:21:31 freeradius1 radiusd[1387]: Received response to status check 221382 (1 in current sequence) Oct 20 10:21:48 freeradius1 radiusd[1387]: No outstanding request was found for reply from host 10.128.5.1 port 1813 - ID 193 Oct 20 10:21:56 freeradius1 radiusd[1387]: No outstanding request was found for reply from host 10.128.5.1 port 1813 - ID 199 Oct 20 10:21:56 freeradius1 radiusd[1387]: No outstanding request was found for reply from host 10.128.5.1 port 1813 - ID 64 Oct 20 10:21:56 freeradius1 radiusd[1387]: No outstanding request was found for reply from host 10.128.5.1 port 1813 - ID 159 Oct 20 10:22:00 freeradius1 radiusd[1387]: Received response to status check 221484 (2 in current sequence) Oct 20 10:22:07 freeradius1 radiusd[1387]: No outstanding request was found for reply from host 10.128.5.1 port 1813 - ID 250 Oct 20 10:22:11 freeradius1 radiusd[1387]: No outstanding request was found for reply from host 10.128.5.1 port 1813 - ID 212 Oct 20 10:22:29 freeradius1 radiusd[1387]: Received response to status check 221591 (3 in current sequence) Oct 20 10:22:29 freeradius1 radiusd[1387]: Marking home server 10.128.5.1 port 1813 alive On Mon, Oct 20, 2014 at 12:25 PM, <A.L.M.Buxey@lboro.ac.uk> wrote:
Hi,
I have two freeradius server. Both of them were working well until. But one the server stopped receiving auth request.
..and it now gets the occasional accounting packet... check you rNAS to see what it thinks its doing with the AAA servers. some kit just do not load balance and are sticky on a working Auth server
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html