Monitoring Splunk

KV Store Fails about once a week

AJSCSA
Loves-to-Learn Lots

Roughly once a week, I'm getting the following errors on my single instance Splunk deployment.

 

KV Store changed status to failed. KVStore process terminated..
12/3/2020, 11:53:25 AM


KV Store process terminated abnormally (exit code 14, status exited with code 14). See mongod.log and splunkd.log for details.
12/3/2020, 11:53:25 AM

 

Now, I can fix the issue, by stopping Splunk, renaming the mongod folder and restarting Splunk but I want to know why I'm getting the errors and how to prevent them in the first place.  Any help or assistance would be greatly appreciated.

Labels (1)
0 Karma

nwuest
Path Finder

Hi @AJSCSA,

These alerts you have referenced in your post, is this the "alert" that pops up when you log into the Webpage?

Can you provide some output as to what the following log shows with lines that pertain to KVStore?

On Linux:
# tail -f /opt/splunk/var/log/splunk/mongod.log

On Windows:
# type /opt/splunk/var/log/splunk/mongod.log
OR
# Get-Content /opt/splunk/var/log/splunk/mongod.log -wait

Do let us know what the results yield!

V/R,
nwuest

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