How to identify :
- On the license manager the following error message will be seen in splunkd.log:
0700 ERROR LMMasterRestHandler - path=/masterlm/usage: Signature mismatch between license slave=splunk.admin.splunk and this License Master. Please make sure that the pass4SymmKey setting in server.conf, under [general], is the same for the License Master and all its slaves from ip=XX.XXX.XXX.XXX
If a signature mismatch is found, some host communicating with the license manager does not have the same pass4SymmKey under general in server.conf.
How to fix it:
- Check the general stanza under "$SPLUNK_home/etc/system/local/server.conf in the license manager.
- Look for pass4Symmkey under the general stanza..
- Take the hashed value and run the following command to decrypt the pass4SymmKey:
./splunk show-decrypted --value
Example:
Linux:
SPLUNK_HOME/bin/./splunk show-decrypted --value '$7$Zzr5echNFJmO9fCJjBbHuZL8aRVuOD5v4Z+psV4nmDV5C4BEGiCA1Q=='
Windows:
C:\opt\splunk\bin>./splunk show-decrypted --value "$7$Zzr5echNFJmO9fCJjBbHuZL8aRVuOD5v4Z+psV4nmDV5C4BEGiCA1Q=="

- By default, pass4SymmKey is changeme.
- Do the same on each peer and compare the results. Make pass4SymmKey match under the general stanza in server.conf on all hosts.
- If they don't match, copy the word or value found after running the command in the license manager and paste it in the pass4Symmkey
$SPLUNK_home/etc/system/local/server.conf in the peer.
- Save the change and restart Splunk for the change to take effect.
- If the issue persists, run the btool command to find more stanzas in the peer using pass4SymmKey.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
28-Sep-2026
|
Initial Release |