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.

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

What Is Splunk? Here’s What You Can Do with Splunk

Hey Splunk Community, we know you know Splunk. You likely leverage its unparalleled ability to ingest, index, ...

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...