<?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: TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key=&amp;quot;Caption&amp;quot;: in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475328#M99728</link>
    <description>&lt;P&gt;The reason for this was that there was one wrongly named sourcetype (unsupported character) on props.conf.&lt;/P&gt;

&lt;P&gt;Before upgrade to 7.x.x it was worked without any errors, but after update it start to write this message to internal log. It also gives error "WARN  TcpOutputProc - Possible duplication of events with channel=source::tcp:10514". That also vanished after fixing sourcetype name.&lt;/P&gt;

&lt;P&gt;--&lt;BR /&gt;
Ismo &lt;/P&gt;</description>
    <pubDate>Mon, 13 Jan 2020 12:49:23 GMT</pubDate>
    <dc:creator>isoutamo</dc:creator>
    <dc:date>2020-01-13T12:49:23Z</dc:date>
    <item>
      <title>TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key="Caption":</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475324#M99724</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;

&lt;P&gt;I get al lot of the following messages on my IX:&lt;BR /&gt;
TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key="Caption":&lt;BR /&gt;
Can anyone explain what this error messages indicate?&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2019 09:38:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475324#M99724</guid>
      <dc:creator>aagehh</dc:creator>
      <dc:date>2019-09-11T09:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key="Caption":</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475325#M99725</link>
      <description>&lt;P&gt;We have the same issue after updated from 6.6.5 to 7.3.2.&lt;/P&gt;

&lt;P&gt;Also our HF -&amp;gt; IDX (cluster) traffic has stalled after that. HF said that IDX stops receiving events and on IDX side the haven't found any (real) reason for that yet. All resources seems to be ok even indexers didn't take events in.&lt;/P&gt;

&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2019 07:21:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475325#M99725</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2019-11-21T07:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key="Caption":</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475326#M99726</link>
      <description>&lt;P&gt;I'd probably do the upgrade again, on both sides (IDX and HF). Are HF and IDX on the same version or did only the IDX got upgraded?&lt;/P&gt;

&lt;P&gt;Skalli&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2019 16:45:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475326#M99726</guid>
      <dc:creator>skalliger</dc:creator>
      <dc:date>2019-11-22T16:45:47Z</dc:date>
    </item>
    <item>
      <title>Re: TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key="Caption":</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475327#M99727</link>
      <description>&lt;P&gt;All nodes has the same splunk version. &lt;/P&gt;

&lt;P&gt;Ismo&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2020 10:33:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475327#M99727</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-01-13T10:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key="Caption":</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475328#M99728</link>
      <description>&lt;P&gt;The reason for this was that there was one wrongly named sourcetype (unsupported character) on props.conf.&lt;/P&gt;

&lt;P&gt;Before upgrade to 7.x.x it was worked without any errors, but after update it start to write this message to internal log. It also gives error "WARN  TcpOutputProc - Possible duplication of events with channel=source::tcp:10514". That also vanished after fixing sourcetype name.&lt;/P&gt;

&lt;P&gt;--&lt;BR /&gt;
Ismo &lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2020 12:49:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TcpInputProc-Encountered-S2S-Exception-Invalid-meta-atom-for-key/m-p/475328#M99728</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-01-13T12:49:23Z</dc:date>
    </item>
  </channel>
</rss>

