Security

forgot pass4SymmKey

Michael
Contributor

I inherited a cluster, setup properly, as far as I know. However, am getting the error:

"Bad Request — editTracker failed, reason='WARN: path=/masterlm/usage: Signature mismatch between license slave=//redacted// and this License Master. Please make sure that the pass4SymmKey setting in server.conf, "

when trying to point new systems to the license master.

I know the fix, but I don't know the plain-text pass4SymmKey phrase...

What are my recovery options?
Thanks!

0 Karma

robgora_deloitt
Path Finder

Best option is to create a new pass4SymmKey under the General Stanza for the Licensing server. You don't have to change the Cluster pass4symmKey. Once you change it for the License server, you can change it through out your cluster. And restart Splunk. This should take care of your issue.

jaracan
Communicator

Hi @robgora_deloitte, do you have the step by step guide on how to change the License Master's pass4SymmKey?

Do we need to enable maintenance mode for the Indexers? Or how do we change the pass4SymmKey on the Indexers?

Regards,
Kevin

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...