<?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: Why is TCP data not being indexed? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281684#M53870</link>
    <description>&lt;P&gt;There's a tick mark on line 10 - is that a typo in the answers post?&lt;/P&gt;

&lt;P&gt;If you change the port from 1920 to something else, does it work?&lt;/P&gt;

&lt;P&gt;When Splunk is stopped on that host, is another process using that port? (&lt;CODE&gt;netstat -an | grep 1920&lt;/CODE&gt;)&lt;/P&gt;</description>
    <pubDate>Thu, 27 Oct 2016 20:41:07 GMT</pubDate>
    <dc:creator>sloshburch</dc:creator>
    <dc:date>2016-10-27T20:41:07Z</dc:date>
    <item>
      <title>Why is TCP data not being indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281682#M53868</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a feed of events coming into my Splunk Heavy Forwarder, but they aren't being indexed, and I'm baffled.  Here's my inputs.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcp://:1918]
index = istr_security 
sourcetype =  bcoat_proxysg
disabled = false

[tcp://:1919]
index = istr_security
sourcetype = bcoat_proxysg_plug
disabled = false
`
[tcp://:1920]
connection_host = dns
source = tcp:1920
index = istr_security
sourcetype = bcoat_proxysg_socks
disabled = false
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;1918 works.  It's been in place for a long time.  We are now sending 1920, but it's not showing up. I checked future events, and looked in the logs for any errors, but can't find any.  I do see these messages, but they seem to be telling me that Splunk is now reading my port.  I did a packet capture, and data is arriving. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;10-26-2016 13:51:47.027 -0400 INFO  TcpInputConfig - IPv4 port 1920 is reserved for raw input
10-26-2016 13:51:47.027 -0400 INFO  TcpInputConfig - IPv4 port 1920 will negotiate new-s2s protocol
10-26-2016 13:51:47.027 -0400 INFO  TcpInputProc - Creating raw Acceptor for IPv4 port 1920 with Non-SSL
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 26 Oct 2016 17:57:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281682#M53868</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2016-10-26T17:57:41Z</dc:date>
    </item>
    <item>
      <title>Re: Why is TCP data not being indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281683#M53869</link>
      <description>&lt;P&gt;What happens if you try:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcp://:1920]
 #connection_host = dns
 #source = tcp:1920
 index = istr_security
 sourcetype = answers_test
 disabled = false

and:
[tcp://:1920]
 #connection_host = dns
 source = tcp:1920
 index = istr_security
 sourcetype = answers_test
 disabled = false

and:

[tcp://:1920]
 connection_host = dns
 source = tcp:1920
 index = istr_security
 sourcetype = answers_test
 disabled = false
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 27 Oct 2016 02:03:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281683#M53869</guid>
      <dc:creator>jwelch_splunk</dc:creator>
      <dc:date>2016-10-27T02:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: Why is TCP data not being indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281684#M53870</link>
      <description>&lt;P&gt;There's a tick mark on line 10 - is that a typo in the answers post?&lt;/P&gt;

&lt;P&gt;If you change the port from 1920 to something else, does it work?&lt;/P&gt;

&lt;P&gt;When Splunk is stopped on that host, is another process using that port? (&lt;CODE&gt;netstat -an | grep 1920&lt;/CODE&gt;)&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2016 20:41:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281684#M53870</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2016-10-27T20:41:07Z</dc:date>
    </item>
    <item>
      <title>Re: Why is TCP data not being indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281685#M53871</link>
      <description>&lt;P&gt;And please confirm that you have no firewalls blocking the traffic, either host based or network based.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Oct 2016 13:43:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281685#M53871</guid>
      <dc:creator>Richfez</dc:creator>
      <dc:date>2016-10-28T13:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: Why is TCP data not being indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281686#M53872</link>
      <description>&lt;P&gt;Fixed.  LTM issue - Splunk was fine. &lt;/P&gt;</description>
      <pubDate>Sat, 29 Oct 2016 22:38:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281686#M53872</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2016-10-29T22:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: Why is TCP data not being indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281687#M53873</link>
      <description>&lt;P&gt;And they found the issue with Splunk!  hahahaha! &lt;/P&gt;</description>
      <pubDate>Sat, 29 Oct 2016 22:39:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281687#M53873</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2016-10-29T22:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Why is TCP data not being indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281688#M53874</link>
      <description>&lt;P&gt;can you please explain what was the issue at LTM side ? I am also facing the same problem ? can you tell me the fix for the same ? anything needs to be done from Splunk side ?? Please reply. Thanks.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jan 2019 08:58:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-TCP-data-not-being-indexed/m-p/281688#M53874</guid>
      <dc:creator>pgadhari</dc:creator>
      <dc:date>2019-01-26T08:58:39Z</dc:date>
    </item>
  </channel>
</rss>

