Deployment Architecture

[SHClustering] one of 3 Searchheads is not starting after apps pushed to the members.

sylim_splunk
Splunk Employee
Splunk Employee

pushed apps to the search head cluster to 3 Searchheads 2 of them working good but one searched URL is not accessible and cannot run searches.

The searchhead appeared to be in restarting loop, logs as below;

2278505_restarting.png

Labels (1)
0 Karma
1 Solution

sylim_splunk
Splunk Employee
Splunk Employee

This turned out to happen on a Searchhead repurposed from a searver previously used as an indexer.

It had "slave-apps" under $SPLUNK_HOME/etc. After removing the directory it stays up and running.

If you have the same symptoms and find the same log message as above, then worth checking the directory.

View solution in original post

0 Karma

sylim_splunk
Splunk Employee
Splunk Employee

This turned out to happen on a Searchhead repurposed from a searver previously used as an indexer.

It had "slave-apps" under $SPLUNK_HOME/etc. After removing the directory it stays up and running.

If you have the same symptoms and find the same log message as above, then worth checking the directory.

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...