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

[kasturea]

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.

[Lorenzo1]

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 😂

[arimaldo]

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.

[kasturea]

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