https://community.splunk.com/t5/Getting-Data-In/Can-you-help-me-with-the-following-health-check-error-for-2/m-p/458206#M93954 <P>I saw that I was receiving the following errors in splunkd.log on the master:</P> <P>11-02-2018 17:53:12.573 +0000 WARN GetRemoteAuthToken - Unable to get authentication token from peeruri="<A href="https://10.111.1.142:8089/services/admin/auth-tokens">https://10.111.1.142:8089/services/admin/auth-tokens</A>". <BR /> 11-02-2018 17:53:12.578 +0000 WARN GetRemoteAuthToken - Unable to get authentication token from peeruri="<A href="https://10.111.1.33:8089/services/admin/auth-tokens">https://10.111.1.33:8089/services/admin/auth-tokens</A>". <BR /> 11-02-2018 17:53:12.579 +0000 WARN DistributedPeer - Peer:<A href="https://10.111.1.142:8089">https://10.111.1.142:8089</A> Failed to get server info from <A href="https://10.111.1.142:8089/services/server/info">https://10.111.1.142:8089/services/server/info</A> response code=401 <BR /> 11-02-2018 17:53:12.579 +0000 WARN DistributedPeer - Peer:<A href="https://10.111.1.33:8089">https://10.111.1.33:8089</A> Failed to get server info from <A href="https://10.111.1.142:8089/services/server/info">https://10.111.1.142:8089/services/server/info</A> response code=401</P> <P>I re-authenticated the search heads to the master node and the health status changed to healthy.</P> Fri, 02 Nov 2018 18:40:17 GMT wendtb 2018-11-02T18:40:17Z https://community.splunk.com/t5/Getting-Data-In/Can-you-help-me-with-the-following-health-check-error-for-2/m-p/458205#M93953 <P>I'm receiving the following error message for health check failures for 2 search heads:</P> <PRE><CODE>Error [00000080] Instance name "XXXX" REST interface to peer is taking longer than 5 seconds to respond on https. Peer may be over subscribed or misconfigured. Check var/log/splunk/splunkd_access.log on the peer Last Connect Time:2018-11-01T12:47:12.000+00:00; Failed 1 out of 191 times., Error [00000100] Instance name "XXXX" REST interface to peer is not responding. Check var/log/splunk/splunkd_access.log on the peer. Last Connect Time:2018-11-01T15:48:22.000+00:00; Failed 190 out of 191 times. </CODE></PRE> <P>I have checked the logs and don't see anything relating to this. Can I get some assistance on how to go about fixing this?</P> Thu, 01 Nov 2018 15:59:10 GMT https://community.splunk.com/t5/Getting-Data-In/Can-you-help-me-with-the-following-health-check-error-for-2/m-p/458205#M93953 wendtb 2018-11-01T15:59:10Z https://community.splunk.com/t5/Getting-Data-In/Can-you-help-me-with-the-following-health-check-error-for-2/m-p/458206#M93954 <P>I saw that I was receiving the following errors in splunkd.log on the master:</P> <P>11-02-2018 17:53:12.573 +0000 WARN GetRemoteAuthToken - Unable to get authentication token from peeruri="<A href="https://10.111.1.142:8089/services/admin/auth-tokens">https://10.111.1.142:8089/services/admin/auth-tokens</A>". <BR /> 11-02-2018 17:53:12.578 +0000 WARN GetRemoteAuthToken - Unable to get authentication token from peeruri="<A href="https://10.111.1.33:8089/services/admin/auth-tokens">https://10.111.1.33:8089/services/admin/auth-tokens</A>". <BR /> 11-02-2018 17:53:12.579 +0000 WARN DistributedPeer - Peer:<A href="https://10.111.1.142:8089">https://10.111.1.142:8089</A> Failed to get server info from <A href="https://10.111.1.142:8089/services/server/info">https://10.111.1.142:8089/services/server/info</A> response code=401 <BR /> 11-02-2018 17:53:12.579 +0000 WARN DistributedPeer - Peer:<A href="https://10.111.1.33:8089">https://10.111.1.33:8089</A> Failed to get server info from <A href="https://10.111.1.142:8089/services/server/info">https://10.111.1.142:8089/services/server/info</A> response code=401</P> <P>I re-authenticated the search heads to the master node and the health status changed to healthy.</P> Fri, 02 Nov 2018 18:40:17 GMT https://community.splunk.com/t5/Getting-Data-In/Can-you-help-me-with-the-following-health-check-error-for-2/m-p/458206#M93954 wendtb 2018-11-02T18:40:17Z