Installation

Master License Server and how to control Slaves?

koshyk
Super Champion

We have got a main "Splunk License Server " with few slaves connecting to it.
As part of automation, whenever slaves are installed a new entry will be added to point to the license server.

./splunk edit licenser-localslave -master_uri 'https://master:port'

This was the case until I changed the logic to make the license handling as part of app. But unfortunately, I can see multiple entries in the Splunk Master, showing reoccurence of the slaves!! i.e. same slaves appearing multiple times.
Is there a way to configure them in a config file from the Master? (or has to be deleted?)

Labels (1)
1 Solution

koshyk
Super Champion

Found the problem.
Whenever the command to add slave is run, it inserts into $SPLUNK_HOME/etc/local/ and other places as well.

The solution is to ensure SPlunk Licenses are part of a single App and configure as
$SPLUNK_HOME/etc/apps/mySplunkLicenseApp/local/server.conf

[license]
master_uri = https://masterLicenseServer:ManagementPort

View solution in original post

davidpaper
Contributor

I downvoted this post because testing!

0 Karma

koshyk
Super Champion

Found the problem.
Whenever the command to add slave is run, it inserts into $SPLUNK_HOME/etc/local/ and other places as well.

The solution is to ensure SPlunk Licenses are part of a single App and configure as
$SPLUNK_HOME/etc/apps/mySplunkLicenseApp/local/server.conf

[license]
master_uri = https://masterLicenseServer:ManagementPort
Get Updates on the Splunk Community!

Index This | How many sides does a circle have?

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

Registration for Splunk University is Now Open!

Are you ready for an adventure in learning?   Brace yourselves because Splunk University is back, and it's ...

Splunkbase | Splunk Dashboard Examples App for SimpleXML End of Life

The Splunk Dashboard Examples App for SimpleXML will reach end of support on Dec 19, 2024, after which no new ...