<?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 Splunk Indexing Acting Up in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306992#M57852</link>
    <description>&lt;P&gt;I'm not sure how to describe this problem.  But I'm hoping someone can help me.&lt;/P&gt;

&lt;P&gt;I have a syslog server receiving Router and Switch traffic.  When it was just switch traffic everything worked perfectly.  When I added router traffic things were fine for a few days.  Now, in splunk web, only traffic to my router is shown.&lt;/P&gt;

&lt;P&gt;Looking at the splunk indexing servers error logs, I see this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;WARN  LineBreakingProcessor - Truncating line because limit of 10000 bytes has been exceeded with a line length &amp;gt;= 13507 - data_source="/opt/splunk/var/log/splunk/remote_searches.log", data_host="servers host name", data_sourcetype="splunkd_remote_searches"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I did a bit of research on Splunk&amp;gt;answers and came across this:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/41648/linebreakingprocessor-truncating-line-because-limit-of-10000-has-been-exceeded.html"&gt;LineBreakingProcessor - Truncating line because limit of 10000 has been exceeded&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;As well as similar results when searching the issue.  That led me to create and update a props.conf file.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::tvit_syslog]
TRUNCATE = 15000
sourcetype = splunkd_remote_searches

#[sourcetype::splunkd_remote_searches]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So far I'm getting nowhere fast.&lt;/P&gt;</description>
    <pubDate>Sat, 24 Feb 2018 00:41:23 GMT</pubDate>
    <dc:creator>TitanAE</dc:creator>
    <dc:date>2018-02-24T00:41:23Z</dc:date>
    <item>
      <title>Splunk Indexing Acting Up</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306992#M57852</link>
      <description>&lt;P&gt;I'm not sure how to describe this problem.  But I'm hoping someone can help me.&lt;/P&gt;

&lt;P&gt;I have a syslog server receiving Router and Switch traffic.  When it was just switch traffic everything worked perfectly.  When I added router traffic things were fine for a few days.  Now, in splunk web, only traffic to my router is shown.&lt;/P&gt;

&lt;P&gt;Looking at the splunk indexing servers error logs, I see this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;WARN  LineBreakingProcessor - Truncating line because limit of 10000 bytes has been exceeded with a line length &amp;gt;= 13507 - data_source="/opt/splunk/var/log/splunk/remote_searches.log", data_host="servers host name", data_sourcetype="splunkd_remote_searches"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I did a bit of research on Splunk&amp;gt;answers and came across this:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/41648/linebreakingprocessor-truncating-line-because-limit-of-10000-has-been-exceeded.html"&gt;LineBreakingProcessor - Truncating line because limit of 10000 has been exceeded&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;As well as similar results when searching the issue.  That led me to create and update a props.conf file.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::tvit_syslog]
TRUNCATE = 15000
sourcetype = splunkd_remote_searches

#[sourcetype::splunkd_remote_searches]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So far I'm getting nowhere fast.&lt;/P&gt;</description>
      <pubDate>Sat, 24 Feb 2018 00:41:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306992#M57852</guid>
      <dc:creator>TitanAE</dc:creator>
      <dc:date>2018-02-24T00:41:23Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Indexing Acting Up</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306993#M57853</link>
      <description>&lt;P&gt;The message from the LineBreakingProcessor is unrelated to your issue. It's telling you that Splunk didn't configure line breaking correctly for Splunk's own sourcetype &lt;CODE&gt;splunkd_remote_searches&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;You mentioned you have a syslog server running. Is the syslog server still receiving data from both routers and switches?&lt;/P&gt;</description>
      <pubDate>Sat, 24 Feb 2018 01:52:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306993#M57853</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2018-02-24T01:52:53Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Indexing Acting Up</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306994#M57854</link>
      <description>&lt;P&gt;Yes.  The syslog server is still receiving traffic.&lt;/P&gt;</description>
      <pubDate>Sat, 24 Feb 2018 02:00:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306994#M57854</guid>
      <dc:creator>tentontitan</dc:creator>
      <dc:date>2018-02-24T02:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Indexing Acting Up</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306995#M57855</link>
      <description>&lt;P&gt;Okay, I'm guessing you're reading the logs written by the syslog server with a forwarder? Common things to check on the forwarder / in its logs forwarded to splunk:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;is the forwarder configured to read the files? &lt;CODE&gt;$SPLUNK_HOME/bin/splunk btool --debug inputs list&lt;/CODE&gt;&lt;/LI&gt;
&lt;LI&gt;any messages containing the log file names in splunkd.log? Read errors, permissions, etc.&lt;/LI&gt;
&lt;LI&gt;is it logging thruput for those log files in metrics.log?&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Sat, 24 Feb 2018 13:22:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Indexing-Acting-Up/m-p/306995#M57855</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2018-02-24T13:22:28Z</dc:date>
    </item>
  </channel>
</rss>

