https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104863#M3893 <P>It appears the search head was trying to take over as the license master, maybe due to a loss of connectivity. I would ensure that the search head in question is a slave to the license master. </P> <P><A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Configurealicenseslave">http://docs.splunk.com/Documentation/Splunk/latest/Admin/Configurealicenseslave</A></P> Thu, 29 Mar 2012 20:24:13 GMT mwhite_splunk 2012-03-29T20:24:13Z https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104862#M3892 <P>We received an error from our main search head(splunk1) when one of our indexers port 8089 connection was blocked to the license master.</P> <P>Error screen shot is attached.</P> <PRE><CODE>Unable to distribute to peer named splunk72-g2-inf at uri <A href="https://x.x.x.x" target="test_blank">https://x.x.x.x</A> because peer as status = 'duplicate license'. duplicate license hashes: ....long list of all the hashes.... Also present on the search head(splunk1.xxx.xxx.com)** </CODE></PRE> <P>It appears that splunk search was disabled and dashboards were not coming up when this one indexer lost connection to the license master. I assumed that only that searches on that indexer would be disabled. Any ideas why this happened?</P> <P>We currently just have a production pool with all the indexers, and search heads assigned to a single pool.</P> Thu, 29 Mar 2012 20:00:44 GMT https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104862#M3892 sonicZ 2012-03-29T20:00:44Z https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104863#M3893 <P>It appears the search head was trying to take over as the license master, maybe due to a loss of connectivity. I would ensure that the search head in question is a slave to the license master. </P> <P><A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Configurealicenseslave">http://docs.splunk.com/Documentation/Splunk/latest/Admin/Configurealicenseslave</A></P> Thu, 29 Mar 2012 20:24:13 GMT https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104863#M3893 mwhite_splunk 2012-03-29T20:24:13Z https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104864#M3894 <P>Hi, well our license master shows the search head has been in the pool. Checking the search head licensing info definitely shows it as a slave to the master.</P> Thu, 29 Mar 2012 21:27:59 GMT https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104864#M3894 sonicZ 2012-03-29T21:27:59Z https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104865#M3895 <P>I've seen situations before where the licensing connection went wonky, and my (quick and dirty) solution was to take the indexer out of the pool, then add it back. YMMV.</P> Thu, 29 Mar 2012 22:09:18 GMT https://community.splunk.com/t5/Deployment-Architecture/unable-to-distribute-to-peer-duplicate-license-hashes/m-p/104865#M3895 sowings 2012-03-29T22:09:18Z