Deployment Architecture

How to resolve this Error: socket_error=connect timeout while bringing search head captain up in GCP instance.

kasturea
Explorer

I am getting below error while bringing up the search head captain. The instance is hosted on Google Cloud Platform:

/services/shcluster/member/consensus/pseudoid/last_known_state?output_mode=json, socket_error=Connect Timeout

I followed the below link to setup the search head clustering:
https://docs.splunk.com/Documentation/Splunk/8.0.1/DistSearch/SHCdeploymentoverview

Also, tried the solution:
https://answers.splunk.com/answers/764708/search-head-cluster-71-presents-status-lineerror-c.html

I am not sure whether this is issue with Splunk or GCP.

Labels (2)
0 Karma

Lorenzo1
Path Finder

so i had this problem and after so much wasting of my time trying to find the problem, it turned out that my management port 8089 was not enabled on the "Security Group" that i was using and the moment i added that port everything worked like magic. And i was able to go to sleep. Lol 😂

0 Karma

arimaldo
Explorer

Did you ever get an answer to this question? I ask because I'm running into a similar situation in the set up of my VMs. Same error message. I validated port connectivity (openssl and curl telnet) so I know that isn't the issue.

0 Karma

kasturea
Explorer

Tried cleaning up the splunk cache and reinstalling the Splunk, still facing the issue.

0 Karma
Get Updates on the Splunk Community!

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Enhance Security Operations with Automated Threat Analysis in the Splunk EcosystemAre you leveraging ...

Splunk Developers: Go Beyond the Dashboard with These .Conf25 Sessions

  Whether you’re building custom apps, diving into SPL2, or integrating AI and machine learning into your ...

Index This | How do you write 23 only using the number 2?

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