I use this guide to deploy my search head cluster.
When I try to bring up the cluster captain (step 5):
/opt/splunk/bin/splunk bootstrap shcluster-captain -servers_list "https://xxx.xxx.xxx.xxx:8089,https://xxx.xxx.xxx.xxx:8089,https://xxx.xxx.xxx.xxx:8089" -auth admin:password
I get an error:
uri=https://xxx.xxx.xxx.xxx:8089/services/shcluster/member/consensus/pseudoid/last_known_state?output_mode=json, error=401 - call not properly authenticated. Is this member using the same pass4SymmKey as other members?; uri=https://xxx.xxx.xxx.xxx:8089/services/shcluster/member/consensus/pseudoid/last_known_state?output_mode=json, error=401 - call not properly authenticated. Is this member using the same pass4SymmKey as other members?;
The pass4SymmKey and the shcluster_label are the same on all cluster members in $SPLUNK_HOME$/ets/system/local/server.conf.
The stanza [shclustering]:
conf_deploy_fetch_url = https://xxx.xxx.xxx.xxx:8089
disabled = 0
mgmt_uri = https://xxx.xxx.xxx.xxx:8089
pass4SymmKey = mykey
shcluster_label = shcluster_test
The deployer is not a member of the search head cluster.
I changed the mgmt portы, but it did not help.
I can not understand what the problem is.
Thanks for the help!
Make sure you restarted the Search Head after you initialized Search Head Clustering
Check whether your mgmt_uri is correct. It needs to point to the local system (whereas conf_deploy_fetch_url points to the Deployer).
hi,
I got the same Problem.
so I solfed it with a password wich is short.
my innitial password was 121 bit long, that doesn't work.
could someone explain what the max bit of PW are?
feel free to mark this post as usefull 😄
Change pass4SymmKey with command:
splunk edit shcluster-config -secret xxxxx