Deployment Architecture

Search Head Cluster - Unable to add Search Head Cluster member - WARN: call not properly authenticated

rbal_splunk
Splunk Employee
Splunk Employee

I'm trying to add a shcluster-member into a search head cluster with a CLI command:

[shclustering]
conf_deploy_fetch_url = https://jack-test-12.sv.splunk.com:8089
disabled = 0
mgmt_uri = https://99.99.999.4:8089
pass4SymmKey = test

The following message shows up in splunkd.log

01-13-2016 16:46:47.742 +0800 WARN  SHPoolingHandler - Failed to proxy call to member. https://jack-test-12.sv.splunk.com:8089 WARN:  call not properly authenticated
01-13-2016 16:46:47.840 +0800 WARN  SHPoolingHandler - Failed to proxy call to member. https://jack-test-12.sv.splunk.com:8089 WARN:  call not properly authenticated
1 Solution

rbal_splunk
Splunk Employee
Splunk Employee

The pass4SymmKey is incorrect, which is why you would receive these error messages and cannot add a new member to the search head cluster.

View solution in original post

rbal_splunk
Splunk Employee
Splunk Employee

The pass4SymmKey is incorrect, which is why you would receive these error messages and cannot add a new member to the search head cluster.

Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...