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!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...