Knowledge Management

Why is KV store initialization failing after fassert() error in mongod.log?

scottrunyon
Contributor

splunkd.log has multiple entries
11-03-2016 06:37:05.137 -0500 ERROR outputcsv - Error in 'outputlookup' command: External command based lookup 'xxxxxxxxxx' is not available because KV Store initialization has failed. Please contact your system administrator.

mongod.log shows
***aborting after fassert() failure

I tried restarting splunk and the result is the same.

0 Karma

Seawheels51
Path Finder

Worked for me, thank you

0 Karma

scottrunyon
Contributor

After looking at several other posts concerning the KV store, I found a clean command

$SPLUNK_HOME/bin/splunk clean kvstore --local

After deleting the mongod.lock file and issuing the clean, the mogod.exe was able to run with out errors.

Reports are now working.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...