topic Re: Failed to start indexer service due to "Cannot disable indexes on a clustering slave". How to resolve it? in Splunk Search

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

jeffreysun — Mon, 07 Aug 2017 05:54:35 GMT

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.

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

esix_splunk — Mon, 07 Aug 2017 06:44:57 GMT

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

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

anand_singh17 — Mon, 21 Aug 2017 13:53:41 GMT

https://answers.splunk.com/answers/406009/why-is-splunk-crashing-whenever-i-try-to-start-the.html