Deployment Architecture

duplicate license

a212830
Champion

Hi,

I am building out a new dev environment, and I just created a bunch of new indexers on brand new vm's. I also setup a search-head, and pointed it at my dev license mgr. So far, so good. However, when I setup distributed-searching, I am getting a "duplicate license" on the new search-head. All the new servers are pointing at my dev license mgr. I logged into my dev license mgr, and looked at the licensing and the distributed-searching, and I don't see that message anywhere.

Any suggestions?

0 Karma
1 Solution

a212830
Champion

Never mind - my bad. License file got moved over by mistake as part of the chef recipe.

View solution in original post

0 Karma

strive
Influencer

Good to know that you found out where it was hiding 🙂

0 Karma

a212830
Champion

Never mind - my bad. License file got moved over by mistake as part of the chef recipe.

0 Karma

strive
Influencer

Which version of splunk you are using? Have you checked that you have not added license on your search head?

Check if this applicable in your case - http://answers.splunk.com/answers/8475/distributed-search-issue-duplicate-licenses

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!

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...