Getting Data In

Can you help me with the following health check error for 2 search heads?: "Error 00000080"

wendtb
Path Finder

I'm receiving the following error message for health check failures for 2 search heads:

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.

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?

Tags (2)
0 Karma
1 Solution

wendtb
Path Finder

I saw that I was receiving the following errors in splunkd.log on the master:

11-02-2018 17:53:12.573 +0000 WARN GetRemoteAuthToken - Unable to get authentication token from peeruri="https://10.111.1.142:8089/services/admin/auth-tokens".
11-02-2018 17:53:12.578 +0000 WARN GetRemoteAuthToken - Unable to get authentication token from peeruri="https://10.111.1.33:8089/services/admin/auth-tokens".
11-02-2018 17:53:12.579 +0000 WARN DistributedPeer - Peer:https://10.111.1.142:8089 Failed to get server info from https://10.111.1.142:8089/services/server/info response code=401
11-02-2018 17:53:12.579 +0000 WARN DistributedPeer - Peer:https://10.111.1.33:8089 Failed to get server info from https://10.111.1.142:8089/services/server/info response code=401

I re-authenticated the search heads to the master node and the health status changed to healthy.

View solution in original post

0 Karma

wendtb
Path Finder

I saw that I was receiving the following errors in splunkd.log on the master:

11-02-2018 17:53:12.573 +0000 WARN GetRemoteAuthToken - Unable to get authentication token from peeruri="https://10.111.1.142:8089/services/admin/auth-tokens".
11-02-2018 17:53:12.578 +0000 WARN GetRemoteAuthToken - Unable to get authentication token from peeruri="https://10.111.1.33:8089/services/admin/auth-tokens".
11-02-2018 17:53:12.579 +0000 WARN DistributedPeer - Peer:https://10.111.1.142:8089 Failed to get server info from https://10.111.1.142:8089/services/server/info response code=401
11-02-2018 17:53:12.579 +0000 WARN DistributedPeer - Peer:https://10.111.1.33:8089 Failed to get server info from https://10.111.1.142:8089/services/server/info response code=401

I re-authenticated the search heads to the master node and the health status changed to healthy.

0 Karma
Get Updates on the Splunk Community!

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...