https://community.splunk.com/t5/Installation/homePath-not-configured/m-p/177278#M2741 <P>Ahha! I <EM>think</EM> 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.</P> <P>In Dev I did a chmod 777 * in /$SPLUNK_HOME and now everything works. </P> <P>So I think that was my issue…. </P> Fri, 23 May 2014 18:29:28 GMT andrewkenth 2014-05-23T18:29:28Z https://community.splunk.com/t5/Installation/homePath-not-configured/m-p/177277#M2740 <P>I upgraded my dev instance today from 6.0 to 6.1.1 and am all of a sudden getting this error:</P> <P>Problem parsing indexes.conf: stanza=charlesriver Required parameter=homePath not configured</P> <P>Which indexes.conf file is this referring to and what does it mean? </P> <P>This is the content of my etc/apps/CharlesRiverInfoSec/local/indexs.conf file:</P> <P>[charlesriver]<BR /> coldPath = $SPLUNK_DB/charlesriver/colddb<BR /> homePath = $SPLUNK_DB/charlesriver/db<BR /> thawedPath = $SPLUNK_DB/charlesriver/thaweddb<BR /> maxTotalDataSizeMB = 500000</P> <P>Obviously I do have a homePath here.</P> Mon, 28 Sep 2020 16:43:03 GMT https://community.splunk.com/t5/Installation/homePath-not-configured/m-p/177277#M2740 andrewkenth 2020-09-28T16:43:03Z https://community.splunk.com/t5/Installation/homePath-not-configured/m-p/177278#M2741 <P>Ahha! I <EM>think</EM> 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.</P> <P>In Dev I did a chmod 777 * in /$SPLUNK_HOME and now everything works. </P> <P>So I think that was my issue…. </P> Fri, 23 May 2014 18:29:28 GMT https://community.splunk.com/t5/Installation/homePath-not-configured/m-p/177278#M2741 andrewkenth 2014-05-23T18:29:28Z