Deployment Architecture

How to fix error: error "Failed to contact license master: reason=WARN: path=/masterlm/usage: invalid signature on request"?

ostendrh
Engager

When upgrading from Splunk Enterprise 6.2.2 to 6.2.5, one no longer sees the license slave on the license master.

Tried copying the encrypted "pass4SymmKey" value in etc/system/local/server.conf from license master to license slave (indexer), and restarting both Splunk instances, however this did not resolve the issue and the error remains.

How to fix this and allow license slave to be seen on license master?

1 Solution

rostendorf_splu
Splunk Employee
Splunk Employee

On Splunk Enterprise 6.2.x, Instead of copying the encrypted value of "pass4SymmKey" from the License master to your slave (indexer server), try entering the unencrypted password that you used when initially creating the "pass4SymmKey" on your license master and then restart the Splunk license slave instance. If you don't remember your password, you can change the value on both the Splunk license master and slave and restart both instances. After restart, the password should be encrypted again.

View solution in original post

rostendorf_splu
Splunk Employee
Splunk Employee

On Splunk Enterprise 6.2.x, Instead of copying the encrypted value of "pass4SymmKey" from the License master to your slave (indexer server), try entering the unencrypted password that you used when initially creating the "pass4SymmKey" on your license master and then restart the Splunk license slave instance. If you don't remember your password, you can change the value on both the Splunk license master and slave and restart both instances. After restart, the password should be encrypted again.

thomas_forbes
Communicator

When I do this it automatically encrypts the password I set for it. I set the password on the license master and all the licenses slaves and restart the slaves. The password on the license slaves encrypts itself. This answer did not work for me.

0 Karma

thomas_forbes
Communicator

Got this fix to work when I got rid of my pass4SymmKey under my [general] stanza in my original server.conf file. Originally I had only (1) pass4SymmKey in the [general] stanza. I then added a pass4SymmKey to the [clustering] stanza creating (2) pass4Symmkeys. It appears as if the (2) keys were conflicting with each other.

Thanks,
Tom Forbes

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

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

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...