<?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: BIND IP Causing issues with RTSearch... in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16900#M2091</link>
    <description>&lt;P&gt;The two functions (BINDIP and Real-time search) do not play well with each other.  This is being tracked as SPL-32549 and we hope to have it addressed in an upcoming maintenance release&lt;/P&gt;</description>
    <pubDate>Thu, 08 Jul 2010 01:03:59 GMT</pubDate>
    <dc:creator>matt</dc:creator>
    <dc:date>2010-07-08T01:03:59Z</dc:date>
    <item>
      <title>BIND IP Causing issues with RTSearch...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16896#M2087</link>
      <description>&lt;P&gt;We have done an interface binding (to IP: index1_IP) on one of our indexers.&lt;/P&gt;

&lt;P&gt;This was done on one of the indexer (indexer1) as testing:&lt;/P&gt;

&lt;P&gt;etc/splunk-launch.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SPLUNK_BINDIP=index1_IP
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;etc/system/local/web.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;mgmtHostPort = index1_IP:8089
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Afterward, we noticed an issue with the live-tail feature on both the search head and indexer:&lt;/P&gt;

&lt;P&gt;search head:  &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;P&gt;[index1] Streamed search execute failed because: Error in 'RealTimeSearch': Failed to connect with url 'https://127.0.0.1:8089/services/streams/rtsearch' because of Encountered a connection error for host 127.0.0.1:8089\n..&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;from index1:  &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;P&gt;Failed to create result provider for remote peer 'index1' at uri '' with the stream 'rtlitsearch ( host=arg1* OR host=arg2* ) arg3 | fields keepcolorder=t * "*" "host" "index" "source" "sourcetype" "splunk_server"'.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;It seems from the error displayed on the search head that it's not tailing the indexer by the correct IP.&lt;/P&gt;

&lt;P&gt;Are we missing more parameter in some conf files in order to bind to the IP successfully?&lt;/P&gt;

&lt;P&gt;Let me know if you guys need any further info. &lt;/P&gt;

&lt;P&gt;Just FYI that we have an open support case for this but we have not heard back from Splunk Support so I am trying Splunk Answers since you guys are always fast and helpful. &lt;/P&gt;

&lt;P&gt;Thanks. &lt;/P&gt;

&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jul 2010 22:12:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16896#M2087</guid>
      <dc:creator>balbano</dc:creator>
      <dc:date>2010-07-06T22:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: BIND IP Causing issues with RTSearch...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16897#M2088</link>
      <description>&lt;P&gt;Hi, 
have you tried this stanza configuration in the etc/system/local/server.conf file?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[httpServerListener:index1_IP:8089]
ssl = true
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 07 Jul 2010 19:20:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16897#M2088</guid>
      <dc:creator>Paolo_Prigione</dc:creator>
      <dc:date>2010-07-07T19:20:42Z</dc:date>
    </item>
    <item>
      <title>Re: BIND IP Causing issues with RTSearch...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16898#M2089</link>
      <description>&lt;P&gt;This did not resolve the issue.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jul 2010 22:05:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16898#M2089</guid>
      <dc:creator>balbano</dc:creator>
      <dc:date>2010-07-07T22:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: BIND IP Causing issues with RTSearch...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16899#M2090</link>
      <description>&lt;P&gt;As a workaround until someone can shed some light on this, we have done the following:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Installed rinetd in order to do port forwarding from 127.0.0.1:8089---&amp;gt;index1_IP:8089...&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;This seems to have fixed the problem until we hear from anyone here or from the support engineers. &lt;/P&gt;

&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jul 2010 23:36:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16899#M2090</guid>
      <dc:creator>balbano</dc:creator>
      <dc:date>2010-07-07T23:36:03Z</dc:date>
    </item>
    <item>
      <title>Re: BIND IP Causing issues with RTSearch...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16900#M2091</link>
      <description>&lt;P&gt;The two functions (BINDIP and Real-time search) do not play well with each other.  This is being tracked as SPL-32549 and we hope to have it addressed in an upcoming maintenance release&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jul 2010 01:03:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/BIND-IP-Causing-issues-with-RTSearch/m-p/16900#M2091</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2010-07-08T01:03:59Z</dc:date>
    </item>
  </channel>
</rss>

