Getting Data In

Trying to set up a distributed management console on the master node of my indexer cluster, why am I getting "duplicate instance name"?

horsefez
Motivator

Hi Splunkers!

I'm about to set up a Distributed Management Console on my Master node of my indexer cluster.
Unfortunately, after I did every step in the manual, the master shows a "duplicate instance name" as I try to apply the settings.

And this is in fact true.
The two indexers that are clustered have an instance (serverName) and a Machine name of their own.
BUT the Instance (host) field has the name of the cluster master node.

(it's similar to this question https://answers.splunk.com/answers/188595/splunk-62-cluster-message-duplicate-instance-name.html?utm...)

THE PROBLEM IS:
I've checked the /splunk/etc/system/local/inputs.conf and server.conf on every indexer peer and they all have their own individual host or servername.

The only thing I don't know about is the config I found in the /default directory which says

[default]
...
host = $decideOnStartup
1 Solution

horsefez
Motivator

Solved it myself.

I applyed a cluster-bundle with a
[default]
host = nameofthemasternode
in the inputs.conf

This was the cause of the error! 🙂

View solution in original post

horsefez
Motivator

Solved it myself.

I applyed a cluster-bundle with a
[default]
host = nameofthemasternode
in the inputs.conf

This was the cause of the error! 🙂

Get Updates on the Splunk Community!

Unlock New Opportunities with Splunk Education: Explore Our Latest Courses!

At Splunk Education, we’re dedicated to providing top-tier learning experiences that cater to every skill ...

Technical Workshop Series: Splunk Data Management and SPL2 | Register here!

Hey, Splunk Community! Ready to take your data management skills to the next level? Join us for a 3-part ...

Spotting Financial Fraud in the Haystack: A Guide to Behavioral Analytics with Splunk

In today's digital financial ecosystem, security teams face an unprecedented challenge. The sheer volume of ...