<?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: failure during peer node setup in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139566#M5262</link>
    <description>&lt;P&gt;You are right. The splunk versions were different. Having the same versions solved this problem.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jan 2015 18:28:36 GMT</pubDate>
    <dc:creator>nivedita_viswan</dc:creator>
    <dc:date>2015-01-27T18:28:36Z</dc:date>
    <item>
      <title>failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139561#M5257</link>
      <description>&lt;P&gt;I get the following error when I try setting up my Peer node:&lt;/P&gt;

&lt;P&gt;Failed to register with cluster master reason: failed method=POST path=/services/cluster/master/peers master=&lt;A href="https://sjcsplunkmstr01-prod.tlcinternal.com:8089" target="_blank"&gt;https://sjcsplunkmstr01-prod.tlcinternal.com:8089&lt;/A&gt; rv=0 actual_response_code=500 expected_response_code=201 status_line=HTTP/1.1 500 Internal Server Error [ event=addPeer status=retrying AddPeerRequest: { _id= active_bundle_id=8ABFFC208D2DCE1B6478276AA0188FC5 add_type=Initial-Add base_generation_id=0 forwarderdata_rcv_port=9997 forwarderdata_use_ssl=0 mgmt_port=8089 name=3A231B5A-EE5D-4F6F-A690-4198A2DE24CC register_forwarder_address= register_replication_address= register_search_address= replication_port=8080 replication_use_ssl=0 replications= server_name=sjcsplunk01-prod.tlcinternal.com status=Up } ].&lt;/P&gt;

&lt;P&gt;On the master node, the following message appears:&lt;/P&gt;

&lt;P&gt;Failed to add peer 'guid=3A231B5A-EE5D-4F6F-A690-4198A2DE24CC server name=sjcsplunk01-prod.tlcinternal.com ip=10.128.16.163:8089' to the master. Error=site not in available_sites&lt;/P&gt;

&lt;P&gt;I have gone through a post which suggests checking the port status. Ports 8080 and 8089 are open. &lt;BR /&gt;
I was able to add one node to the cluster, only the 2nd node fails. However, the failing node was acting as a stand-alone indexer before, whereas the added node was a new installation.&lt;/P&gt;

&lt;P&gt;What could be the reason for this failure?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:41:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139561#M5257</guid>
      <dc:creator>nivedita_viswan</dc:creator>
      <dc:date>2020-09-28T17:41:45Z</dc:date>
    </item>
    <item>
      <title>Re: failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139562#M5258</link>
      <description>&lt;P&gt;what version of splunk are u running?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; Error=site not in available_sites
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;claims that the peer does not have the right 'site' set up, if multisite is turned on, every peer must have a 'site' that is listed in the master's 'available_sites' setting (server.conf). if multisite is turned off, the peers should not have a 'site' attribute&lt;/P&gt;</description>
      <pubDate>Thu, 25 Sep 2014 01:18:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139562#M5258</guid>
      <dc:creator>dxu_splunk</dc:creator>
      <dc:date>2014-09-25T01:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139563#M5259</link>
      <description>&lt;P&gt;We are using the latest version - 6.1.3 of Splunk. Multisite is turned off and peers dont have a 'site' attribute in the peer server.conf files.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Sep 2014 17:22:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139563#M5259</guid>
      <dc:creator>nivedita_viswan</dc:creator>
      <dc:date>2014-09-25T17:22:13Z</dc:date>
    </item>
    <item>
      <title>Re: failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139564#M5260</link>
      <description>&lt;P&gt;is the peer not the same version as the master?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Sep 2014 19:04:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139564#M5260</guid>
      <dc:creator>dxu_splunk</dc:creator>
      <dc:date>2014-09-25T19:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139565#M5261</link>
      <description>&lt;P&gt;Yesterday I had the similar issue. The rootcause was the indexer had the 6.0.2 and Cluster Master with 6.1.3. After upgrading the indexers to 6.1.3 (same version as CM), the problem resolved. &lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2015 15:22:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139565#M5261</guid>
      <dc:creator>jayannah</dc:creator>
      <dc:date>2015-01-27T15:22:21Z</dc:date>
    </item>
    <item>
      <title>Re: failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139566#M5262</link>
      <description>&lt;P&gt;You are right. The splunk versions were different. Having the same versions solved this problem.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2015 18:28:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139566#M5262</guid>
      <dc:creator>nivedita_viswan</dc:creator>
      <dc:date>2015-01-27T18:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139567#M5263</link>
      <description>&lt;P&gt;I am having the same issue as the above, but both master and peer nodes are on the same versions (6.2.4, build 271043). Any ideas on what is causing it?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2015 17:27:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139567#M5263</guid>
      <dc:creator>z5pate</dc:creator>
      <dc:date>2015-07-23T17:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139568#M5264</link>
      <description>&lt;P&gt;do you have multisite turned on, but did not set the site on the indexer? (or vice versa)&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2015 20:22:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139568#M5264</guid>
      <dc:creator>dxu_splunk</dc:creator>
      <dc:date>2015-07-23T20:22:58Z</dc:date>
    </item>
    <item>
      <title>Re: failure during peer node setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139569#M5265</link>
      <description>&lt;P&gt;Mulitsite is not turned on. Here are the server.conf for Master and Peer nodes:&lt;/P&gt;

&lt;P&gt;MASTER NODE:&lt;/P&gt;

&lt;P&gt;[sslConfig]&lt;BR /&gt;
sslKeysfilePassword = $1$cGranKIu+bsX&lt;/P&gt;

&lt;P&gt;[lmpool:auto_generated_pool_download-trial]&lt;BR /&gt;
description = auto_generated_pool_download-trial&lt;BR /&gt;
quota = MAX&lt;BR /&gt;
slaves = *&lt;BR /&gt;
stack_id = download-trial&lt;/P&gt;

&lt;P&gt;[lmpool:auto_generated_pool_forwarder]&lt;BR /&gt;
description = auto_generated_pool_forwarder&lt;BR /&gt;
quota = MAX&lt;BR /&gt;
slaves = *&lt;BR /&gt;
stack_id = forwarder&lt;/P&gt;

&lt;P&gt;[lmpool:auto_generated_pool_free]&lt;BR /&gt;
description = auto_generated_pool_free&lt;BR /&gt;
quota = MAX&lt;BR /&gt;
slaves = *&lt;BR /&gt;
stack_id = free&lt;/P&gt;

&lt;P&gt;[general]&lt;BR /&gt;
pass4SymmKey = $1$JyaOwOdosukX&lt;BR /&gt;
serverName = splunkp01&lt;BR /&gt;
site = default&lt;/P&gt;

&lt;P&gt;[clustering]&lt;BR /&gt;
access_logging_for_heartbeats = 1&lt;BR /&gt;
max_peer_build_load = 5&lt;BR /&gt;
mode = master&lt;BR /&gt;
pass4SymmKey = $1$Nz6D2+5m7t8=&lt;BR /&gt;
replication_factor = 2&lt;BR /&gt;
search_factor = 1&lt;/P&gt;

&lt;P&gt;[lmpool:auto_generated_pool_enterprise]&lt;BR /&gt;
description = auto_generated_pool_enterprise&lt;BR /&gt;
quota = MAX&lt;BR /&gt;
slaves = *&lt;BR /&gt;
stack_id = enterprise&lt;/P&gt;

&lt;P&gt;[license]&lt;BR /&gt;
active_group = Enterprise&lt;/P&gt;

&lt;P&gt;PEER NODE:&lt;/P&gt;

&lt;P&gt;[sslConfig]&lt;BR /&gt;
sslKeysfilePassword = $1$nG7D0aK47qLW&lt;/P&gt;

&lt;P&gt;[lmpool:auto_generated_pool_download-trial]&lt;BR /&gt;
description = auto_generated_pool_download-trial&lt;BR /&gt;
quota = MAX&lt;BR /&gt;
slaves = *&lt;BR /&gt;
stack_id = download-trial&lt;/P&gt;

&lt;P&gt;[lmpool:auto_generated_pool_forwarder]&lt;BR /&gt;
description = auto_generated_pool_forwarder&lt;BR /&gt;
quota = MAX&lt;BR /&gt;
slaves = *&lt;BR /&gt;
stack_id = forwarder&lt;/P&gt;

&lt;P&gt;[lmpool:auto_generated_pool_free]&lt;BR /&gt;
description = auto_generated_pool_free&lt;BR /&gt;
quota = MAX&lt;BR /&gt;
slaves = *&lt;BR /&gt;
stack_id = free&lt;/P&gt;

&lt;P&gt;[general]&lt;BR /&gt;
pass4SymmKey = $1$yyKXjef+pfDW&lt;BR /&gt;
serverName = splunkp02&lt;BR /&gt;
site = default&lt;/P&gt;

&lt;P&gt;[clustering]&lt;BR /&gt;
master_uri = &lt;A href="https://xxx.xxx.xxx.50:8089" target="_blank"&gt;https://xxx.xxx.xxx.50:8089&lt;/A&gt;&lt;BR /&gt;
mode = slave&lt;BR /&gt;
pass4SymmKey = $1$2zqalu7w+cY=&lt;/P&gt;

&lt;P&gt;[lmpool:auto_generated_pool_enterprise]&lt;BR /&gt;
description = auto_generated_pool_enterprise&lt;BR /&gt;
quota = MAX&lt;BR /&gt;
slaves = *&lt;BR /&gt;
stack_id = enterprise&lt;/P&gt;

&lt;P&gt;[license]&lt;BR /&gt;
active_group = Enterprise&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:32:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/failure-during-peer-node-setup/m-p/139569#M5265</guid>
      <dc:creator>z5pate</dc:creator>
      <dc:date>2020-09-29T07:32:05Z</dc:date>
    </item>
  </channel>
</rss>

