homePath not configured


I upgraded my dev instance today from 6.0 to 6.1.1 and am all of a sudden getting this error:

Problem parsing indexes.conf: stanza=charlesriver Required parameter=homePath not configured

Which indexes.conf file is this referring to and what does it mean?

This is the content of my etc/apps/CharlesRiverInfoSec/local/indexs.conf file:

coldPath = $SPLUNK_DB/charlesriver/colddb
homePath = $SPLUNK_DB/charlesriver/db
thawedPath = $SPLUNK_DB/charlesriver/thaweddb
maxTotalDataSizeMB = 500000

Obviously I do have a homePath here.

Tags (2)
0 Karma


Ahha! I think I figured it out. I copied the upgrade file over as my own user then untarred it as you should as the application user. I think the permissions on the files then retained MY (not the application user) id’s permissions causing a bunch of permissions issues.

In Dev I did a chmod 777 * in /$SPLUNK_HOME and now everything works.

So I think that was my issue….

0 Karma
Get Updates on the Splunk Community!

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...

Last Chance to Submit Your Paper For BSides Splunk - Deadline is August 12th!

Hello everyone! Don't wait to submit - The deadline is August 12th! We have truly missed the community so ...