<?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 New Install - TailingProcessor - Could not send data to output queue (parsingQueue), retrying… in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/New-Install-TailingProcessor-Could-not-send-data-to-output-queue/m-p/94325#M19622</link>
    <description>&lt;P&gt;After installing Splunk on a new node as a LightWeightForwarder and configuring for the local logs I wanted to monitor I started seeing the following messages in the splunkd.log:&lt;/P&gt;

&lt;P&gt;TailingProcessor - Could not send data to output queue (parsingQueue), retrying…&lt;/P&gt;

&lt;P&gt;These messages only occurred after I added the file monitors, it had run overnight with just the unix application without issue.&lt;/P&gt;</description>
    <pubDate>Thu, 25 Nov 2010 02:49:27 GMT</pubDate>
    <dc:creator>mikelanghorst</dc:creator>
    <dc:date>2010-11-25T02:49:27Z</dc:date>
    <item>
      <title>New Install - TailingProcessor - Could not send data to output queue (parsingQueue), retrying…</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/New-Install-TailingProcessor-Could-not-send-data-to-output-queue/m-p/94325#M19622</link>
      <description>&lt;P&gt;After installing Splunk on a new node as a LightWeightForwarder and configuring for the local logs I wanted to monitor I started seeing the following messages in the splunkd.log:&lt;/P&gt;

&lt;P&gt;TailingProcessor - Could not send data to output queue (parsingQueue), retrying…&lt;/P&gt;

&lt;P&gt;These messages only occurred after I added the file monitors, it had run overnight with just the unix application without issue.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2010 02:49:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/New-Install-TailingProcessor-Could-not-send-data-to-output-queue/m-p/94325#M19622</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2010-11-25T02:49:27Z</dc:date>
    </item>
    <item>
      <title>Re: New Install - TailingProcessor - Could not send data to output queue (parsingQueue), retrying…</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/New-Install-TailingProcessor-Could-not-send-data-to-output-queue/m-p/94326#M19623</link>
      <description>&lt;P&gt;I realized after seeing this message that I hadn't manually inspected the directories the monitors were looking at.  I had over 1000 old webserver logs that I was telling splunk to forward over to the indexer, causing it to backup with the maxKBps setting by default.&lt;/P&gt;

&lt;P&gt;I chose to cleanout the old files to reduce what i was indexing, but altering the maxKBps would work as well to help clear out the backlog.  &lt;A href="http://answers.splunk.com/questions/7750/increase-throughput-limit-on-a-lightweight-forwarder" rel="nofollow"&gt;http://answers.splunk.com/questions/7750/increase-throughput-limit-on-a-lightweight-forwarder&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Chatting about it on IRC, this may be a common issue on cold installs.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2010 02:54:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/New-Install-TailingProcessor-Could-not-send-data-to-output-queue/m-p/94326#M19623</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2010-11-25T02:54:05Z</dc:date>
    </item>
  </channel>
</rss>

