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.

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...