<?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: Splunk upgrade 9.3 to 9.4 mongodb error in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/711138#M21585</link>
    <description>&lt;P&gt;I have the same issue&lt;/P&gt;</description>
    <pubDate>Mon, 10 Feb 2025 11:43:57 GMT</pubDate>
    <dc:creator>dominikatvastli</dc:creator>
    <dc:date>2025-02-10T11:43:57Z</dc:date>
    <item>
      <title>Splunk upgrade 9.3 to 9.4 mongodb error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/709807#M21438</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;Upgrading on prem from 9.3 to 9.4 and getting this error on mongod which Iv never had before:&lt;/P&gt;&lt;P&gt;The server certificate does not match the host name. Hostname: 127.0.0.1 does not match SAN(s):&lt;/P&gt;&lt;P&gt;This makes sense since I am using a custom cert and 127.0.0.1 isnt on it, the cert is a wildcard cert I use internally so messing with the hosts file wont work, is there a way to get mongod to either ignore the cer SAN's or to change the connect string for mongo so that its connecting to the FQDN rather than 127.0.0.1&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jan 2025 09:08:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/709807#M21438</guid>
      <dc:creator>Warren_Laya</dc:creator>
      <dc:date>2025-01-27T09:08:19Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk upgrade 9.3 to 9.4 mongodb error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/711138#M21585</link>
      <description>&lt;P&gt;I have the same issue&lt;/P&gt;</description>
      <pubDate>Mon, 10 Feb 2025 11:43:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/711138#M21585</guid>
      <dc:creator>dominikatvastli</dc:creator>
      <dc:date>2025-02-10T11:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk upgrade 9.3 to 9.4 mongodb error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/711272#M21601</link>
      <description>&lt;P&gt;I dont have a resoluton here, this is the documentation and the issue is around certs but I still cant work out where im going wrong.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.4.0/Admin/MigrateKVstore" target="_blank"&gt;Upgrade the KV store server version - Splunk Documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Im just going to wait for a new version where this is resolved.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 14:49:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/711272#M21601</guid>
      <dc:creator>Warren_Laya</dc:creator>
      <dc:date>2025-02-11T14:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk upgrade 9.3 to 9.4 mongodb error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/712638#M21722</link>
      <description>&lt;P&gt;If you're still experiencing issues, please take a look here&amp;nbsp;&lt;A href="https://splunk.my.site.com/customer/s/article/KV-store-status-failed-after-upgrade-to-9-4" target="_blank"&gt;https://splunk.my.site.com/customer/s/article/KV-store-status-failed-after-upgrade-to-9-4&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The suggestion of concatenating CA certs resolved the errors and Splunk was able to upgrade/initialize kvstore after a restart of splunkd.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 20:09:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/712638#M21722</guid>
      <dc:creator>n8o</dc:creator>
      <dc:date>2025-02-26T20:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk upgrade 9.3 to 9.4 mongodb error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/712659#M21724</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;i don't know if it is the same issue but could you check this requirements. For example, is your cpu supported avx / avx2 instructions, if yes, is it enabled ?&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.4.0/Admin/MigrateKVstore" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.4.0/Admin/MigrateKVstore&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.mongodb.com/docs/manual/administration/production-notes/" target="_blank"&gt;https://www.mongodb.com/docs/manual/administration/production-notes/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;i hope this help&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 23:46:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/712659#M21724</guid>
      <dc:creator>myitlab42000</dc:creator>
      <dc:date>2025-02-26T23:46:15Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk upgrade 9.3 to 9.4 mongodb error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/741114#M21806</link>
      <description>&lt;P&gt;If you use Splunk Cloud, the issue might be related to the splunkclouduf.spl credential package. There is a workaround:&lt;/P&gt;&lt;P&gt;&lt;A href="https://splunk.my.site.com/customer/s/article/KV-store-status-failed-after-upgrade-to-9-4" target="_blank" rel="noopener"&gt;https://splunk.my.site.com/customer/s/article/KV-store-status-failed-after-upgrade-to-9-4&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Be aware that you will have to combine these three certs&amp;nbsp;&lt;SPAN class=""&gt;&lt;SPAN&gt;(instead of the two included in the guide) &lt;/SPAN&gt;&lt;/SPAN&gt;in this order for the Find more Apps page to work properly:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="cpp"&gt;$SPLUNK_HOME/etc/auth/appsCA.pem
$SPLUNK_HOME/etc/auth/cacert.pem
$SPLUNK_HOME/etc/apps/100_&amp;lt;stackname&amp;gt;_splunkcloud/default/&amp;lt;stackname&amp;gt;_cacert.pem&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2025 12:52:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/741114#M21806</guid>
      <dc:creator>bluelobster</dc:creator>
      <dc:date>2025-03-07T12:52:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk upgrade 9.3 to 9.4 mongodb error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/741215#M21823</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;i think that this is the correct instruction for this case&amp;nbsp;&lt;A href="https://splunk.my.site.com/customer/s/article/KV-Store-Error-after-upgrading-Splunk-Enterprise" target="_blank"&gt;https://splunk.my.site.com/customer/s/article/KV-Store-Error-after-upgrading-Splunk-Enterprise&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The issue is with server name, not with CA.&lt;/P&gt;&lt;P&gt;So try to disable sslVerifyServerName attribute like above instruction is guided.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Sat, 08 Mar 2025 15:37:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-upgrade-9-3-to-9-4-mongodb-error/m-p/741215#M21823</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2025-03-08T15:37:21Z</dc:date>
    </item>
  </channel>
</rss>

