Installation

homePath not configured

andrewkenth
Communicator

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:

[charlesriver]
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

andrewkenth
Communicator

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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...