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

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!

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

March Community Office Hours Security Series Uncovered!

Hello Splunk Community! In March, Splunk Community Office Hours spotlighted our fabulous Splunk Threat ...

Stay Connected: Your Guide to April Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars in April. This post ...