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!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk on November 6 at 11AM PT, and empower your SOC to reach new heights! Duration: ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...