Getting Data In

Attempting to run Splunk, why am I getting "Problem parsing indexes.conf: Cannot create index 3rdIndex: path of homePath must be absolute"?

athoma31
Explorer
[volume:primary]
path = opt/splunk/splunk_data
maxVolumeDataSizeMB = 2000000

[3rdIndex]
homePath   = volume:primary/3rdIndex/db
coldPath   = volume:cold/3rdIndex/colddb
thawedPath = $SPLUNK_DB/3rdIndex/thaweddb
maxDataSize = auto_high_volume

When attempting to run splunk, it results in the message:

Problem parsing indexes.conf: Cannot create index 3rdIndex: path of homePath must be absolute ('opt/splunk/splunk_data/3rdIndex/db') 

What's strange is that I have other indexers with the same stanzas in indexes.conf, except that on those, the volume definitions were split to a separate indexes.conf. Any ideas?

0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

Prepend a slash to your primary volume path and try again.

View solution in original post

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Prepend a slash to your primary volume path and try again.

0 Karma

athoma31
Explorer

There's no telling how many times I overlooked that simple mistake. Thanks!

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 ...