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!

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...

[Live Demo] Watch SOC transformation in action with the reimagined Splunk Enterprise ...

Overwhelmed SOC? Splunk ES Has Your Back Tool sprawl, alert fatigue, and endless context switching are making ...

What’s New & Next in Splunk SOAR

Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us on ...