<?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 Re: KVStore error after upgrade to 9.0.1 in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/KVStore-error-after-upgrade-to-9-0-1-Stand-alone-commands/m-p/621846#M14596</link>
    <description>&lt;P&gt;I just had customer with similar issue on Windows HF.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;First there was the problem of expired cert.&amp;nbsp; This was not just the&amp;nbsp;&lt;/P&gt;&lt;P&gt;/opt/splunk/etc/auth/server.pem but also the pfx file in same location,&lt;BR /&gt;And because of the way certs are managed on Windows in Splunk 9.x it was also necessary to delete via&amp;nbsp;&lt;BR /&gt;Windows Cert Management in Local / Personal / Certificates...Delete SplunkServerDefaultCert&lt;BR /&gt;&lt;BR /&gt;This got us past the expired cert issue...&lt;BR /&gt;But then we found mongod.log detected Mongo version as "db version v4.2.19"....&lt;BR /&gt;But then a few lines later complained about....&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;F CONTROL [initandlisten] ** IMPORTANT: UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion document (ERROR: BadValue: Invalid value for version, found 3.6, expected '4.2' or '4.0'. Contents of featureCompatibilityVersion document in admin.system.version: { _id: "featureCompatibilityVersion", version: "3.6"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;So we had to cd to Splunk_Home/var/run/splunk/kvstore_upgrade&lt;BR /&gt;Renamed versionFile42 to versionFile42.old&lt;BR /&gt;Run the&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.0/Admin/MigrateKVstore#Migrate_manually_to_the_latest_version_of_Mongo_DB" target="_self"&gt; standalone migration command again&lt;/A&gt;...&lt;BR /&gt;&lt;SPAN&gt;splunk migrate migrate-kvstore&lt;BR /&gt;&lt;/SPAN&gt;Start Splunk, KVStore working!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 23 Nov 2022 12:18:17 GMT</pubDate>
    <dc:creator>dwest_splunk</dc:creator>
    <dc:date>2022-11-23T12:18:17Z</dc:date>
    <item>
      <title>KVStore error after upgrade to 9.0.1- Stand alone commands</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/KVStore-error-after-upgrade-to-9-0-1-Stand-alone-commands/m-p/617732#M14268</link>
      <description>&lt;P&gt;I just went through this so posting here as I could not find the commands to fix it and had to open a ticket with support. Root cause was one of my servers had the server.pem certificate expired. This prevented the KV Store upgrade from working during the upgrade. This was on a windows heavy forwarder. Those are standalone, all the docs have commands for a SH cluster. So here are the standalone commands, hoping this helps someone. Took me a while to get them out of support.&lt;/P&gt;
&lt;P&gt;./splunk migrate kvstore-storage-engine --target-engine wiredTiger&lt;/P&gt;
&lt;P&gt;./splunk migrate migrate-kvstore&lt;/P&gt;
&lt;P&gt;./splunk show kvstore-status --verbose&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Lee.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 13:48:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/KVStore-error-after-upgrade-to-9-0-1-Stand-alone-commands/m-p/617732#M14268</guid>
      <dc:creator>leekeener</dc:creator>
      <dc:date>2022-11-23T13:48:15Z</dc:date>
    </item>
    <item>
      <title>Re: KVStore error after upgrade to 9.0.1</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/KVStore-error-after-upgrade-to-9-0-1-Stand-alone-commands/m-p/621846#M14596</link>
      <description>&lt;P&gt;I just had customer with similar issue on Windows HF.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;First there was the problem of expired cert.&amp;nbsp; This was not just the&amp;nbsp;&lt;/P&gt;&lt;P&gt;/opt/splunk/etc/auth/server.pem but also the pfx file in same location,&lt;BR /&gt;And because of the way certs are managed on Windows in Splunk 9.x it was also necessary to delete via&amp;nbsp;&lt;BR /&gt;Windows Cert Management in Local / Personal / Certificates...Delete SplunkServerDefaultCert&lt;BR /&gt;&lt;BR /&gt;This got us past the expired cert issue...&lt;BR /&gt;But then we found mongod.log detected Mongo version as "db version v4.2.19"....&lt;BR /&gt;But then a few lines later complained about....&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;F CONTROL [initandlisten] ** IMPORTANT: UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion document (ERROR: BadValue: Invalid value for version, found 3.6, expected '4.2' or '4.0'. Contents of featureCompatibilityVersion document in admin.system.version: { _id: "featureCompatibilityVersion", version: "3.6"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;So we had to cd to Splunk_Home/var/run/splunk/kvstore_upgrade&lt;BR /&gt;Renamed versionFile42 to versionFile42.old&lt;BR /&gt;Run the&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.0/Admin/MigrateKVstore#Migrate_manually_to_the_latest_version_of_Mongo_DB" target="_self"&gt; standalone migration command again&lt;/A&gt;...&lt;BR /&gt;&lt;SPAN&gt;splunk migrate migrate-kvstore&lt;BR /&gt;&lt;/SPAN&gt;Start Splunk, KVStore working!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 12:18:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/KVStore-error-after-upgrade-to-9-0-1-Stand-alone-commands/m-p/621846#M14596</guid>
      <dc:creator>dwest_splunk</dc:creator>
      <dc:date>2022-11-23T12:18:17Z</dc:date>
    </item>
  </channel>
</rss>

