<?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 Status:failed in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/656113#M9664</link>
    <description>&lt;P&gt;Feels like I tried every suggestion here, from renaming the cert, generating my own, messing around with the windows cert store and the .conf files... And this solution finally worked! Thank you so much!!&lt;/P&gt;</description>
    <pubDate>Wed, 30 Aug 2023 13:55:34 GMT</pubDate>
    <dc:creator>dwthomas16</dc:creator>
    <dc:date>2023-08-30T13:55:34Z</dc:date>
    <item>
      <title>Kvstore Status:failed</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/649566#M9615</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;Please help.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a AIO Splunk Enterprise &lt;STRONG&gt;Ver: 8.1.2&lt;/STRONG&gt; setup running on &lt;STRONG&gt;windows server&lt;/STRONG&gt;, i have done the following upgrade:&lt;/P&gt;&lt;P&gt;1. Upgrade from &lt;STRONG&gt;Ver: 8.1.2&lt;/STRONG&gt; to &lt;STRONG&gt;ver: 8.2.5&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;2. checked &lt;STRONG&gt;kvstore&lt;/STRONG&gt; already migrated to &lt;STRONG&gt;wireTiger&lt;/STRONG&gt;. So no migration done on my end.&lt;/P&gt;&lt;P&gt;3. Upgrade from &lt;STRONG&gt;Ver: 8.2.5&lt;/STRONG&gt; to &lt;STRONG&gt;Ver: 9.0.5&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;After start up checked &lt;STRONG&gt;kvstore&lt;/STRONG&gt; with the command&amp;nbsp;&lt;STRONG&gt;"splunk show kvstore-status --verbose",&amp;nbsp;&lt;/STRONG&gt;as shown below is the result:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;WARNING: Server Certificate Hostname Validation is disabled. Please see server.conf/[sslConfig]/cliverifyServerName for details.&lt;/P&gt;&lt;P&gt;This member:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; BackupRestoreStatus : Ready&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;disables : 0&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;featureCompaitibilityVersion : An error occured during the last operation ('getParameter', domain:&amp;nbsp; '15', code: '13053'): No Suitable servers found: '&lt;STRONG&gt;serxxxx&lt;/STRONG&gt; SelectionTimeoutMS' expired: [connection closed calling ismaster on '127.0.0.1:8191']&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; guid : DAxxxxxx-xxxx-xxx-xxxx-xxxxxxxxxxxx&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; port : 8191&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;standalone : 1&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;status : failed&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;storageEngine : wireTiger&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone advise why after upgraded to Ver: 9.0.5 kvstore failed? i have tried the following but the status still showed &lt;STRONG&gt;failed&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;Point 2: Take KV store backup&lt;/P&gt;&lt;P&gt;2.1. stop Splunk.&lt;BR /&gt;2.2. take backup of the DB (keep it safe - may be needed in emergency):&lt;BR /&gt;2.3. cp -r $SPLUNK_DB/kvstore/mongo /backup&lt;BR /&gt;2.4. Rename mongod.lock (Location: $SPLUNK_DB/kvstore/mongod) : mongod.lock_bkp&lt;/P&gt;&lt;P&gt;Point 3: clean up KVStore Splunk&lt;/P&gt;&lt;P&gt;3.1 Stop the member: ./splunk stop&lt;BR /&gt;3.2 Clean the member's kvstore: ./splunk clean kvstore --local&lt;BR /&gt;3.3 start Splunk&lt;/P&gt;&lt;P&gt;Point 4.&amp;nbsp;Check kvstore status on each node.&lt;BR /&gt;./splunkshow kvstore-status&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help. Thank you&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 02:26:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/649566#M9615</guid>
      <dc:creator>Spinner79</dc:creator>
      <dc:date>2023-07-07T02:26:09Z</dc:date>
    </item>
    <item>
      <title>Re: Kvstore Status:failed</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/655840#M9662</link>
      <description>&lt;P&gt;Were you able to find a solution to this? I'm having the same issue.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 13:15:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/655840#M9662</guid>
      <dc:creator>dwthomas16</dc:creator>
      <dc:date>2023-08-28T13:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: Kvstore Status:failed</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/655904#M9663</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried the follow the link&amp;nbsp;&lt;A href="https://splunkonbigdata.com/failed-to-start-kv-store-process-see-mongod-log-and-splunkd-log-for-details/" target="_blank"&gt;https://splunkonbigdata.com/failed-to-start-kv-store-process-see-mongod-log-and-splunkd-log-for-details/&lt;/A&gt;&amp;nbsp;, surprisingly after restart everything back to normal.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2023 02:00:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/655904#M9663</guid>
      <dc:creator>Spinner79</dc:creator>
      <dc:date>2023-08-29T02:00:58Z</dc:date>
    </item>
    <item>
      <title>Re: Kvstore Status:failed</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/656113#M9664</link>
      <description>&lt;P&gt;Feels like I tried every suggestion here, from renaming the cert, generating my own, messing around with the windows cert store and the .conf files... And this solution finally worked! Thank you so much!!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 13:55:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/656113#M9664</guid>
      <dc:creator>dwthomas16</dc:creator>
      <dc:date>2023-08-30T13:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: Kvstore Status:failed</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/656182#M9665</link>
      <description>&lt;P&gt;Glad that you have managed to resolve the issue like me.&lt;/P&gt;&lt;P&gt;I went through high &amp;amp; low searching for the solutions as well.&lt;/P&gt;&lt;P&gt;Luckily managed to Google out the link I sent you and resolved the issue.&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/245034"&gt;@dwthomas16&lt;/a&gt;&amp;nbsp;Happy Splunking.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 03:54:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/656182#M9665</guid>
      <dc:creator>Spinner79</dc:creator>
      <dc:date>2023-08-31T03:54:07Z</dc:date>
    </item>
    <item>
      <title>Re: Kvstore Status:failed</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/696045#M10234</link>
      <description>&lt;P&gt;Just happened to us now... Do we know if this fixed it and\or what was the initial cause.&amp;nbsp; This was just after a splunkd restart.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2024 17:07:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Kvstore-Status-failed/m-p/696045#M10234</guid>
      <dc:creator>cmeisch</dc:creator>
      <dc:date>2024-08-12T17:07:49Z</dc:date>
    </item>
  </channel>
</rss>

