Getting Data In

Duplicate GUIDS for standalone indexers, how can I safely correct this?

davebo1896
Communicator

Just noticed I have a duplicate GUID for two standalone, load balanced (via splunk conf, not F5) indexers.
Can I just delete /opt/splunk/etc/instance.cfg and restart one of the indexers, or will that cause some issues?

Tags (3)
0 Karma
1 Solution

davebo1896
Communicator

Well, not sure if this the right answer, but I gave it a try (splunk stop;rm /opt/splunk/etc/instance.cfg; splunk start) and everything seems to be fine.

View solution in original post

davebo1896
Communicator

Well, not sure if this the right answer, but I gave it a try (splunk stop;rm /opt/splunk/etc/instance.cfg; splunk start) and everything seems to be fine.

Get Updates on the Splunk Community!

The Splunk Success Framework: Your Guide to Successful Splunk Implementations

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

Splunk Training for All: Meet Aspiring Cybersecurity Analyst, Marc Alicea

Splunk Education believes in the value of training and certification in today’s rapidly-changing data-driven ...

Investigate Security and Threat Detection with VirusTotal and Splunk Integration

As security threats and their complexities surge, security analysts deal with increased challenges and ...