Installation

Is there a way to update the slave_name when connecting to the license master?

djfang
Explorer

Hi,

I'm wondering if there's a way to update the slave_name when connecting to the license master. My slave_name is the same across all my imaged indexers as I am trying to deploy them in my test environment. The identical slave_name is causing my license master usage report to only report one of the slaves.

Thanks in advance for any pointers.

Cheers!

Labels (1)
0 Karma
1 Solution

djfang
Explorer

I realized that the problem causing this was the GUID setting under /opt/splunk/etc/instance.cfg
It was using the same GUID as the other slaves (due to direct image copy of instances with splunk preinstalled).
All I had to do was to remove the guid and restart Splunk. It will autogenerate with a new GUID. Then connections to the Splunk license master will be seen as one.

In instance.cfg

[general]
guid =

View solution in original post

djfang
Explorer

I realized that the problem causing this was the GUID setting under /opt/splunk/etc/instance.cfg
It was using the same GUID as the other slaves (due to direct image copy of instances with splunk preinstalled).
All I had to do was to remove the guid and restart Splunk. It will autogenerate with a new GUID. Then connections to the Splunk license master will be seen as one.

In instance.cfg

[general]
guid =

lguinn2
Legend

The "slave name" is actually the Splunk server name from server.conf
You really should update server.conf, so that not all of your test servers have the same name...

AFIAK, you cannot do this on the license master. It should be done on each of the license slaves. This will also make other reports and tools (like the Distributed Management Console) work better.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

Splunk is officially part of Cisco

Revolutionizing how our customers build resilience across their entire digital footprint.   Splunk ...

Splunk APM & RUM | Planned Maintenance March 26 - March 28, 2024

There will be planned maintenance for Splunk APM and RUM between March 26, 2024 and March 28, 2024 as ...