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

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

scottrunyon — Thu, 03 Nov 2016 12:39:06 GMT

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.

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

scottrunyon — Thu, 03 Nov 2016 17:24:52 GMT

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.

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

Seawheels51 — Fri, 13 Dec 2024 13:49:23 GMT

Worked for me, thank you