<?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: Setting up Splunk receiver through TCP/IP in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-Splunk-receiver-through-TCP-IP/m-p/49360#M9385</link>
    <description>&lt;P&gt;Caio, is this on a unix box?&lt;BR /&gt;
If so, there might be a permission issue as only root can open ports under 1024.&lt;BR /&gt;
You can try listening to tcp on a higher port, say 9001. 
Let us know if you get similar errors then.&lt;BR /&gt;
Cheers,&lt;BR /&gt;
.gz&lt;/P&gt;</description>
    <pubDate>Tue, 14 Sep 2010 04:09:25 GMT</pubDate>
    <dc:creator>Genti</dc:creator>
    <dc:date>2010-09-14T04:09:25Z</dc:date>
    <item>
      <title>Setting up Splunk receiver through TCP/IP</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-Splunk-receiver-through-TCP-IP/m-p/49358#M9383</link>
      <description>&lt;P&gt;Hey everybody,&lt;/P&gt;

&lt;P&gt;I'm going through some problems trying to set my receiver splunk instance.
I performed exactely the ways which is described on the documantation, although Im still getting one error when I attempt to save my new date TCP input.&lt;/P&gt;

&lt;P&gt;That's the error:&lt;/P&gt;

&lt;P&gt;Encountered the following error while trying to save: In handler 'raw': TCP port 333 is not available.&lt;/P&gt;

&lt;P&gt;As I said before, I followed each step on the docs, but for sure I'm missing something.
I am sorry if I am being an ignorant, but I'm just starting with splunk.&lt;/P&gt;

&lt;P&gt;Thank you in advance.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Sep 2010 03:42:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-up-Splunk-receiver-through-TCP-IP/m-p/49358#M9383</guid>
      <dc:creator>Caio_Santos</dc:creator>
      <dc:date>2010-09-14T03:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up Splunk receiver through TCP/IP</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-Splunk-receiver-through-TCP-IP/m-p/49359#M9384</link>
      <description>&lt;P&gt;Is something else running on port 333 already?  At the command line, try running &lt;CODE&gt;netstat -an&lt;/CODE&gt; to check.&lt;/P&gt;

&lt;P&gt;Also, if you are running Splunk as a non-root user, Splunk will not be able to bind to ports below 1024, as those ports are considered privileged.&lt;/P&gt;

&lt;P&gt;Do you have the same problem with other port numbers, especially with port numbers above 1024?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Sep 2010 03:51:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-up-Splunk-receiver-through-TCP-IP/m-p/49359#M9384</guid>
      <dc:creator>southeringtonp</dc:creator>
      <dc:date>2010-09-14T03:51:34Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up Splunk receiver through TCP/IP</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-Splunk-receiver-through-TCP-IP/m-p/49360#M9385</link>
      <description>&lt;P&gt;Caio, is this on a unix box?&lt;BR /&gt;
If so, there might be a permission issue as only root can open ports under 1024.&lt;BR /&gt;
You can try listening to tcp on a higher port, say 9001. 
Let us know if you get similar errors then.&lt;BR /&gt;
Cheers,&lt;BR /&gt;
.gz&lt;/P&gt;</description>
      <pubDate>Tue, 14 Sep 2010 04:09:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-up-Splunk-receiver-through-TCP-IP/m-p/49360#M9385</guid>
      <dc:creator>Genti</dc:creator>
      <dc:date>2010-09-14T04:09:25Z</dc:date>
    </item>
  </channel>
</rss>

