Getting Data In

New Install - TailingProcessor - Could not send data to output queue (parsingQueue), retrying…

mikelanghorst
Motivator

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:

TailingProcessor - Could not send data to output queue (parsingQueue), retrying…

These messages only occurred after I added the file monitors, it had run overnight with just the unix application without issue.

1 Solution

mikelanghorst
Motivator

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.

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. http://answers.splunk.com/questions/7750/increase-throughput-limit-on-a-lightweight-forwarder

Chatting about it on IRC, this may be a common issue on cold installs.

View solution in original post

mikelanghorst
Motivator

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.

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. http://answers.splunk.com/questions/7750/increase-throughput-limit-on-a-lightweight-forwarder

Chatting about it on IRC, this may be a common issue on cold installs.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...