Installation

kvstore failing to start

tinscore
New Member

Trying to run splunk in a docker container - which I can successfully get running.

however...

Once I try to add a persistent volume for /splunkhome/var and /splunkhome/etc, the kvstore fails to start.

The persistent volume is being hosted on a NAS (synology diskstation) which is being mounted to my linux host via SMB (cifs) with the local admin of the NAS - so I should have full permissions to the share.

I've been able to observe the following error

"homePath='/opt/splunk/var/lib/splunk/audit/db' of index=_audit on unusable filesystem."

are SMB file shares not supposed by splunk?

I can get past this error by adding "OPSIMISTIC_ABOUT_FILE_LOCKING = 1"
to splunk-launch.conf

but then I get stuck with where kvstore failing to start.  kvstore logs indicate it's because the permissions are too open - even though I've changed them to 400.

 

Any insight from your beautiful minds?

Labels (1)
0 Karma

BartZm
New Member

You need to unmount "/opt/splunk/var/lib/splunk/kvstore/mongo" folder.

Eg. in docker-compose

volumes:
- "/home/docker_volumes/etc:/opt/splunk/etc"
- "/home/docker_volumes/var:/opt/splunk/var"
- "/opt/splunk/var/lib/splunk/kvstore/mongo"

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...