Splunk Search

Failed to start indexer service due to "Cannot disable indexes on a clustering slave". How to resolve it?

jeffreysun
New Member

Here are the error logs.

08-07-2017 05:44:10.836 +0000 INFO DatabaseDirectoryManager - idx=wineventlog Writing a bucket manifest in hotWarmPath=‘/usr/local/splunk/var/lib/splunk/wineventlog/db’, pendingBucketUpdates=0 . Reason=‘Refreshing manifest at start-up.’
08-07-2017 05:44:10.837 +0000 INFO DatabaseDirectoryManager - idx=winevents Writing a bucket manifest in hotWarmPath=‘/usr/local/splunk/var/lib/splunk/winevents/db’, pendingBucketUpdates=0 . Reason=‘Refreshing manifest at start-up.’
08-07-2017 05:44:10.837 +0000 FATAL IndexerService - One or more indexes could not be initialized. Cannot disable indexes on a clustering slave.

Tags (1)
0 Karma

esix_splunk
Splunk Employee
Splunk Employee

Most likely you have edited the configuration files locally on that indexer. In an indexer cluster, you need to edit the configuration bundle on the CLuster Master Node, and then deploy that to the cluster. Your members cant have different configurations when part of a cluster...

See Here : http://docs.splunk.com/Documentation/Splunk/6.6.2/Indexer/Updatepeerconfigurations

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...