Deployment Architecture

unable to distribute to peer - unable to get auth token - READ TIMEOUT

bcyates
Communicator

We Just migrated two SH Vms to a new data center. Now we are having intermitten timeouts to where the search heads cannot distribute to peers and I am seeing this error message

WARN GetRemoteAuthToken - Unable to get auth token from peer: https://xx.xx.xxx:8089 due to: Read Timeout; exceeded 60000 milliseconds

0 Karma

mstjohn_splunk
Splunk Employee
Splunk Employee

Hi @bycyates. Did you figure out how to solve this problem? If so, would you mind describing what you did as an answer so other users could learn from your work? Thanks!

0 Karma

mayurr98
Super Champion

Hello
I suspect as you have migrated two SH Vms to a new data center there may be a connectivity issue
This usually appears when the search head cannot authenticate with search peers in the distributed environment. Pls re-authenticate either using CLI or from the GUI within the search head : settings-> distributed search -> Search peers and ensure, its up and enabled.

0 Karma

deepashri_123
Motivator

Hey@bcyates,

This looks like authentication error. I think it is related to the distServerKeys being regenerated.
Also check the cluster pass4symmkey.

Let me know if this helps!!!

0 Karma
Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...