<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic KVStore mongo db failing to start, after kvstore is restored from backup in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/KVStore-mongo-db-failing-to-start-after-kvstore-is-restored-from/m-p/312636#M66868</link>
    <description>&lt;P&gt;I have restored my kvstore from backup using the steps from here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.0.1/Admin/BackupKVstore" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/7.0.1/Admin/BackupKVstore&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;But now the SHC node's kvstore cannot start.  Here are the messages seen in mongod.log:&lt;BR /&gt;
     2018-01-19T20:34:36.865Z I JOURNAL  [initandlisten] journal dir=/opt/splunk/var/lib/splunk/kvstore/mongo/journal&lt;BR /&gt;
     2018-01-19T20:34:36.865Z I JOURNAL  [initandlisten] recover begin&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I JOURNAL  [initandlisten] info no lsn file in journal/ directory&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I JOURNAL  [initandlisten] recover lsn: 0&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I JOURNAL  [initandlisten] recover /opt/splunk/var/lib/splunk/kvstore/mongo/journal/j._0&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I JOURNAL  [initandlisten] recover applying initial journal section with sequence number 65&lt;BR /&gt;
     2018-01-19T20:34:36.866Z F JOURNAL  [initandlisten] dbexception during recovery: 15923 couldn't get file length when opening mapping /opt/splunkvar/lib/splunk/kvstore/mongo/local.0 boost::filesystem::file_size: No such file or directory: "/opt/splunkvar/lib/splunk/kvstore/mongo/local.0"&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] exception in initAndListen: 15923 couldn't get file length when opening mapping /opt/splunk/var/lib/splunk/kvstore/mongo/local.0 boost::filesystem::file_size: No such file or directory: "/opt/splunk/var/lib/splunk/kvstore/mongo/local.0", terminating&lt;BR /&gt;
     2018-01-19T20:34:36.866Z W REPL     [initandlisten] ReplicationCoordinatorImpl::shutdown() called before startReplication() finished.  Shutting down without cleaning up the replication system&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I CONTROL  [initandlisten] now exiting&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I NETWORK  [initandlisten] shutdown: going to close listening sockets...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I NETWORK  [initandlisten] shutdown: going to flush diaglog...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I NETWORK  [initandlisten] shutdown: going to close sockets...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] shutdown: waiting for fs preallocator...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] shutdown: final commit...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] shutdown: closing all files...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] closeAllFiles() finished&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 17:41:44 GMT</pubDate>
    <dc:creator>splunkIT</dc:creator>
    <dc:date>2020-09-29T17:41:44Z</dc:date>
    <item>
      <title>KVStore mongo db failing to start, after kvstore is restored from backup</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/KVStore-mongo-db-failing-to-start-after-kvstore-is-restored-from/m-p/312636#M66868</link>
      <description>&lt;P&gt;I have restored my kvstore from backup using the steps from here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.0.1/Admin/BackupKVstore" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/7.0.1/Admin/BackupKVstore&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;But now the SHC node's kvstore cannot start.  Here are the messages seen in mongod.log:&lt;BR /&gt;
     2018-01-19T20:34:36.865Z I JOURNAL  [initandlisten] journal dir=/opt/splunk/var/lib/splunk/kvstore/mongo/journal&lt;BR /&gt;
     2018-01-19T20:34:36.865Z I JOURNAL  [initandlisten] recover begin&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I JOURNAL  [initandlisten] info no lsn file in journal/ directory&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I JOURNAL  [initandlisten] recover lsn: 0&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I JOURNAL  [initandlisten] recover /opt/splunk/var/lib/splunk/kvstore/mongo/journal/j._0&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I JOURNAL  [initandlisten] recover applying initial journal section with sequence number 65&lt;BR /&gt;
     2018-01-19T20:34:36.866Z F JOURNAL  [initandlisten] dbexception during recovery: 15923 couldn't get file length when opening mapping /opt/splunkvar/lib/splunk/kvstore/mongo/local.0 boost::filesystem::file_size: No such file or directory: "/opt/splunkvar/lib/splunk/kvstore/mongo/local.0"&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] exception in initAndListen: 15923 couldn't get file length when opening mapping /opt/splunk/var/lib/splunk/kvstore/mongo/local.0 boost::filesystem::file_size: No such file or directory: "/opt/splunk/var/lib/splunk/kvstore/mongo/local.0", terminating&lt;BR /&gt;
     2018-01-19T20:34:36.866Z W REPL     [initandlisten] ReplicationCoordinatorImpl::shutdown() called before startReplication() finished.  Shutting down without cleaning up the replication system&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I CONTROL  [initandlisten] now exiting&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I NETWORK  [initandlisten] shutdown: going to close listening sockets...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I NETWORK  [initandlisten] shutdown: going to flush diaglog...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I NETWORK  [initandlisten] shutdown: going to close sockets...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] shutdown: waiting for fs preallocator...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] shutdown: final commit...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] shutdown: closing all files...&lt;BR /&gt;
     2018-01-19T20:34:36.866Z I STORAGE  [initandlisten] closeAllFiles() finished&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 17:41:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/KVStore-mongo-db-failing-to-start-after-kvstore-is-restored-from/m-p/312636#M66868</guid>
      <dc:creator>splunkIT</dc:creator>
      <dc:date>2020-09-29T17:41:44Z</dc:date>
    </item>
    <item>
      <title>Re: KVStore mongo db failing to start, after kvstore is restored from backup</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/KVStore-mongo-db-failing-to-start-after-kvstore-is-restored-from/m-p/312637#M66869</link>
      <description>&lt;P&gt;looks like it's missing /splunk/var/lib/splunk/kvstore/mongo/local.* file which stores the cluster information.&lt;BR /&gt;
You may want to check if you have /opt/splunkvar/lib/splunk/kvstore/mongo/local.0 file existing from your kvstore backup.&lt;/P&gt;

&lt;P&gt;Also if by any chance you did run "splunk clean kvstore --cluster" command after restoring the kvstore backup, it would wipe out all the local.* files which contains the cluster information.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Aug 2018 08:09:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/KVStore-mongo-db-failing-to-start-after-kvstore-is-restored-from/m-p/312637#M66869</guid>
      <dc:creator>scheng_splunk</dc:creator>
      <dc:date>2018-08-16T08:09:38Z</dc:date>
    </item>
  </channel>
</rss>

