<?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: distributed search issue - duplicate licenses in Installation</title>
    <link>https://community.splunk.com/t5/Installation/distributed-search-issue-duplicate-licenses/m-p/79698#M1305</link>
    <description>&lt;P&gt;That was it!  I thought I had changed licenses prior to setting up distributed searches but didn't.  Thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 29 Oct 2010 03:28:02 GMT</pubDate>
    <dc:creator>castle1126</dc:creator>
    <dc:date>2010-10-29T03:28:02Z</dc:date>
    <item>
      <title>distributed search issue - duplicate licenses</title>
      <link>https://community.splunk.com/t5/Installation/distributed-search-issue-duplicate-licenses/m-p/79696#M1303</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;My old, primary Splunk indexer/search head is being retired (v4.1.4).  In its place is 4 new indexing servers that are carrying the indexing load for me (all running v4.1.5).  Each of these 4 systems were built from scratch, with indexes.conf being moved to them.&lt;/P&gt;

&lt;P&gt;I'm trying to set this old server to be a search head for the new systems, allowing it to run some scheduled searches this weekend before we retire the server.  When I add the search peers to the old system via the GUI, they all go in nicely without complaint.  When I log back into the old server's GUI again I get this message on the top of my browser:&lt;/P&gt;

&lt;P&gt;Unable to distribute to peer named xxx at uri &lt;A href="https://xxxx:8089" rel="nofollow"&gt;https://xxxx:8089&lt;/A&gt; because peer has status = "Duplicate License".&lt;/P&gt;

&lt;P&gt;When I look at Manager-&amp;gt;Distributed search-&amp;gt; Search Peers I see the 4 peers showing a status of "duplicate license".&lt;/P&gt;

&lt;P&gt;I've dug around through logs on all systems and nothing pops out as being in error, etc.&lt;/P&gt;

&lt;P&gt;Any ideas?&lt;/P&gt;</description>
      <pubDate>Fri, 29 Oct 2010 01:16:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/distributed-search-issue-duplicate-licenses/m-p/79696#M1303</guid>
      <dc:creator>castle1126</dc:creator>
      <dc:date>2010-10-29T01:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: distributed search issue - duplicate licenses</title>
      <link>https://community.splunk.com/t5/Installation/distributed-search-issue-duplicate-licenses/m-p/79697#M1304</link>
      <description>&lt;P&gt;Sounds like you still have your old license installed on your old indexer/new search head, and you used the same license at one (or all?) of the new indexers.&lt;/P&gt;

&lt;P&gt;At the search head you want to &lt;A href="http://www.splunk.com/base/Documentation/latest/Installation/AboutSplunklicenses#Forwarder_license" rel="nofollow"&gt;change the license to the Forwarder license&lt;/A&gt; (as long as it doesn't do any indexing) and your troubles will go away.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Oct 2010 02:02:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/distributed-search-issue-duplicate-licenses/m-p/79697#M1304</guid>
      <dc:creator>ftk</dc:creator>
      <dc:date>2010-10-29T02:02:00Z</dc:date>
    </item>
    <item>
      <title>Re: distributed search issue - duplicate licenses</title>
      <link>https://community.splunk.com/t5/Installation/distributed-search-issue-duplicate-licenses/m-p/79698#M1305</link>
      <description>&lt;P&gt;That was it!  I thought I had changed licenses prior to setting up distributed searches but didn't.  Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 29 Oct 2010 03:28:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/distributed-search-issue-duplicate-licenses/m-p/79698#M1305</guid>
      <dc:creator>castle1126</dc:creator>
      <dc:date>2010-10-29T03:28:02Z</dc:date>
    </item>
  </channel>
</rss>

