Getting Data In

Accidentally uploaded the same license on indexers and master node. How to resolve a "Duplicated license situation"?

vikas_gopal
Builder

Hi Experts,

I got a situation. By mistake, I uploaded the same license that I used for Indexers and Master node. Now I am getting an error on master node:

"Duplicated License situation happen on peer(master node address) because it has the same license key (key) as this searchhead=search head address"

Even if I stop the search head on which I mistakenly uploaded the license, I am still getting the same error on master node. Can someone suggest how I can resolve this issue?

Thanks
VG

0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi vikas_gopal,
When you have to use a licence on more than one Splunk Serveryou have to:

  • choose one server as License Master [Settings -- Licenses -- Add License] inserting your license;
  • configure all the other Splunk servers as Slave of the License Master [Settings -- Licenses -- Change in Slave] inserting the URL of the Master License (https://xxx.xxx.xxx.xxx:8089)

Bye.
Giuseppe

View solution in original post

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi vikas_gopal,
When you have to use a licence on more than one Splunk Serveryou have to:

  • choose one server as License Master [Settings -- Licenses -- Add License] inserting your license;
  • configure all the other Splunk servers as Slave of the License Master [Settings -- Licenses -- Change in Slave] inserting the URL of the Master License (https://xxx.xxx.xxx.xxx:8089)

Bye.
Giuseppe

0 Karma
Get Updates on the Splunk Community!

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...