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!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...