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!

Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey

Survey for Splunk Admins and App Developers is open now! | Earn a $35 gift card!      Hello there,  Splunk ...

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...