<?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: How do I troubleshoot &amp;quot;ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain&amp;quot;? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163092#M6103</link>
    <description>&lt;P&gt;adding the -auth argument doesn't make a difference.  It just prevents you from getting prompted for credentials.  &lt;/P&gt;</description>
    <pubDate>Wed, 05 Aug 2015 16:14:39 GMT</pubDate>
    <dc:creator>pj_elia</dc:creator>
    <dc:date>2015-08-05T16:14:39Z</dc:date>
    <item>
      <title>How do I troubleshoot "ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain"?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163087#M6098</link>
      <description>&lt;P&gt;I am performing an initial deployment of Splunk Enterprise on 6.2.2.  I have configured a deployer with a recommended secret key in the [shclustering] section of the deployer's server.conf.  I have also initialized three different search head cluster members and restarted splunkd on all members.  When I attempt to bootstrap the initial cluster captain, I receive the simple error, "ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain."&lt;/P&gt;

&lt;P&gt;Does anyone have any guidance on how I can get passed this?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Apr 2015 16:42:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163087#M6098</guid>
      <dc:creator>dnewburg</dc:creator>
      <dc:date>2015-04-22T16:42:13Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot "ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain"?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163088#M6099</link>
      <description>&lt;P&gt;We are having the same issue in the same scenario.  Looking for a solution now....we are using 6.2.4 on linux&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jul 2015 21:00:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163088#M6099</guid>
      <dc:creator>pj_elia</dc:creator>
      <dc:date>2015-07-31T21:00:49Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot "ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain"?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163089#M6100</link>
      <description>&lt;P&gt;What node are you bootstrapping from?&lt;/P&gt;

&lt;P&gt;Post your configs and syntax you are using to create this. If you follow the docs, it should work correctly. So most likely you're missing steps.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2015 14:05:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163089#M6100</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2015-08-01T14:05:25Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot "ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain"?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163090#M6101</link>
      <description>&lt;P&gt;I ran the following on each of the 3 search heads (splunk1,2,3) after installing splunk, configuring them as License slaves, and changing the admin passwords.  &lt;/P&gt;

&lt;P&gt;/opt/splunk/bin/splunk init shcluster-config -mgmt_uri &lt;A href="https://splunkdeployer:8089" target="_blank"&gt;https://splunkdeployer:8089&lt;/A&gt; -replication_port 9200 -secret XXXXX&lt;/P&gt;

&lt;P&gt;Then I ran this on one of the search heads:&lt;/P&gt;

&lt;P&gt;/opt/splunk/bin/splunk bootstrap shcluster-captain -servers_list &lt;A href="https://splunk1.acml.com:8089,https://splunk2.acml.com:8089,https://splunk3.acml.com:8089" target="_blank"&gt;https://splunk1.acml.com:8089,https://splunk2.acml.com:8089,https://splunk3.acml.com:8089&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;and got the following...&lt;/P&gt;

&lt;P&gt;In handler 'shclustermemberconsensus': Failed to Set Configuration. One potential is captain could not hear back from all the nodes in a timeout period. Ensure alladded nodes are up, and increase the raft timeout. If all nodes are up and runningat splunkd.log for appendEntries errors due to mgmt_uri mismatch&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 06:56:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163090#M6101</guid>
      <dc:creator>pj_elia</dc:creator>
      <dc:date>2020-09-29T06:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot "ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain"?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163091#M6102</link>
      <description>&lt;P&gt;There is mistake in your CLI  which you are running on search head.&lt;/P&gt;

&lt;P&gt;Try this &lt;BR /&gt;
replace admin:changed by your Splunk credentials&lt;/P&gt;

&lt;P&gt;/opt/splunk/bin/splunk bootstrap shcluster-captain -servers_list "&lt;A href="https://splunk1.acml.com:8089,https://splunk2.acml.com:8089,https://splunk3.acml.com:8089"&gt;https://splunk1.acml.com:8089,https://splunk2.acml.com:8089,https://splunk3.acml.com:8089&lt;/A&gt;" -auth admin:changed&lt;/P&gt;

&lt;P&gt;Refer follow document&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.4/DistSearch/SHCdeploymentoverview"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.4/DistSearch/SHCdeploymentoverview&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;point 5  Bring up the cluster captain&lt;/P&gt;

&lt;P&gt;I hope this helps &lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2015 07:32:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163091#M6102</guid>
      <dc:creator>ArchanaC</dc:creator>
      <dc:date>2015-08-05T07:32:34Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot "ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain"?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163092#M6103</link>
      <description>&lt;P&gt;adding the -auth argument doesn't make a difference.  It just prevents you from getting prompted for credentials.  &lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2015 16:14:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163092#M6103</guid>
      <dc:creator>pj_elia</dc:creator>
      <dc:date>2015-08-05T16:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot "ERROR SHPRaftConsensus - Failed to bootstrap this node as a captain"?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163093#M6104</link>
      <description>&lt;P&gt;Kindly tear down whole search head clustering setup.&lt;/P&gt;

&lt;P&gt;Edit  server.conf in $SPLUNK_HOME/etc/system/local  and remove [shclustering] and [replication_port] stanza from each  search head and restart them.&lt;/P&gt;

&lt;P&gt;Also remove [shclustering] stanza from server.conf on deployer in $SPLUNK_HOME/etc/system/local and restart.&lt;/P&gt;

&lt;P&gt;In my case I first followed above steps and then did whole clustering setup and it worked.&lt;/P&gt;

&lt;P&gt;don't forget to restart search heads and deployer after tearing the setup.&lt;/P&gt;

&lt;P&gt;I hope this helps.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 06:56:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-troubleshoot-quot-ERROR-SHPRaftConsensus-Failed-to/m-p/163093#M6104</guid>
      <dc:creator>ArchanaC</dc:creator>
      <dc:date>2020-09-29T06:56:09Z</dc:date>
    </item>
  </channel>
</rss>

