Security
Highlighted

Signature mismatch between license slave - but key/secret are the same

Explorer

I reinstalled Splunk with clustering today. The problem is that I keep getting 'Signature mismatch between license slave' errors. I have the same Splunk Secret on all servers. Therefore I added the key already encrypted with the Splunk Secret in the server.conf for the installation.
I have already tried the following things:

  • Decrypt Pass4SymmKey: works!
  • Pass4SymmKey into 'etc/system/local/server.conf': No effect!
  • New pass4SymmKey added: No effect!
  • Reinstalled: No effect!

Is this a bug or am I missing something fundamental?

Thanks for your help.

Rafael

Labels (1)
0 Karma
Highlighted

Re: Signature mismatch between license slave - but key/secret are the same

Motivator

The pass4SymmKey in the [general] stanza must match across your entire cluster.

For indexer clustering, the pass4SymmKey must also be set in the [clustering] stanza on the master and all indexers, and obviously match.

Master:
[clustering]
mode = master
pass4SymmKey = indexclusterpw
...

Indexers:
[clustering]
mode = slave
pass4SymmKey = indexclusterpw
...

Highlighted

Re: Signature mismatch between license slave - but key/secret are the same

Motivator

Also, be sure to add the pass4SymmKey in plain text and cycle Splunk. Don't copy over the encrypted value from another host.

0 Karma
Highlighted

Re: Signature mismatch between license slave - but key/secret are the same

Explorer

It matches across thze entire cluster.

0 Karma
Highlighted

Re: Signature mismatch between license slave - but key/secret are the same

Motivator

Are you running the license master on a dedicated node or one that also performs another Splunk role?

0 Karma
Highlighted

Re: Signature mismatch between license slave - but key/secret are the same

Explorer

I solved the problem. Look the post below. Thank for your help.

0 Karma
Highlighted

Re: Signature mismatch between license slave - but key/secret are the same

Motivator

Glad to help!

0 Karma
Highlighted

Re: Signature mismatch between license slave - but key/secret are the same

Explorer

Hi

I solved the problem with a work colleague. The problem wasn't that the signature didn't match. The error was that I accidentally entered a remote URI for the license master on the license master. However, the remote URI pointed to the server itself. But that doesn't work. The error message is simply misleading.

Greetings Rafael

View solution in original post

0 Karma