All Apps and Add-ons

Splunk on Splunk: After upgrading to Splunk 6.2, why won't the splunkd service if I have an indexes.conf file in the local folder under etc\apps\sos?

DBland
Engager

Splunkd log has the message problem parsing indexes.conf: stanza=summary_forwarders Required parameter=homePath not configured

hexx
Splunk Employee
Splunk Employee

I think that for some reason, you may have a partial definition for the "summary_forwarders" index in %SPLUNK_HOME%\etc\apps\sos\local. This index is not related to the S.o.S app. To the best of my knowledge, it is part of the Deployment Monitor app, which I assume you had installed at one point in the past.

If you don't have that app anymore, my recommendation would be to remove that index definition from the file in question, or to remove %SPLUNK_HOME%\etc\apps\sos\local\indexes.confaltogether if that is the only thing that it contains.

Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

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 GA in US-AWS!

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