Deployment Architecture

How to set a new pass4SymmKey password on a search head cluster deployer?

Raghav2384
Motivator

Hello,

We have a Search head cluster in our environment and the person who set up the Deployer initially forgot the pass4SymmKey. Now , as a result, it's not letting me deploy content and throws the following message

Error while deploying apps to first member: ConfDeploymentException: Error while fetching apps baseline on target=https://xyz.abc.com:8089 Non-200/201 status_code=401; {"messages":[{"type":"WARN","text":"call not properly authenticated"}]}

Now the Cluster is running fine, but it's just that I can't deploy apps/content to the SHC members. Can I set a new password on the server.conf under the shclustering stanza (On Deployer) and add the same pass4SymmKey = new password to SHC members? Does it work, or do I need to re-initialize SHC members after adding the new password?

Appreciate your inputs...I just want to hear if you experts have an alternative before I do it the hard way 😞

Thanks,
Raghav

1 Solution

Raghav2384
Motivator

Thank you all for helping me with this...This is what worked for me

1.I added the new password to deployer and restarted splunkd
2.I initialized SHC process on each SHC member followed by a restart
./splunk init shcluster-config -auth xxx:xxx -mgmt_uri xxx:8089 -replication_port xxx -replication_factor x -conf_deploy_fetch_url xxx:8089 -secret
3.All the SHC members complain that they are not part of the cluster or yet to join (Looks scary but that message makes sense)
4. Now i can push content from deployer

Splunk docs says otherwise

Note the following:

See "Deploy a search head cluster" for details on the splunk init shcluster-config command, including the meaning of the various parameters.
The conf_deploy_fetch_url parameter specifies the URL and management port for the deployer instance. You must set it when adding a new member to an existing cluster, so that the member can immediately contact the deployer for the latest configuration bundle, if any. See "Use the deployer to distribute apps and configuration updates."
This step is for new members only. Do not run it on members rejoining the cluster.

It worked in my case. SHC and Deployer is happily married now.

Thanks,
Raghav

View solution in original post

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...