Getting Data In

The TCP output processor has paused the data flow

Wierengaaj
Loves-to-Learn

I recently transitioned to a new instance of Splunk and have been having some trouble configuring the new environment. 

I have 8 remote Windows hosts with identical forwarders (inputs.conf and outputs.conf are the same on all 8). 5 of the hosts are forwarding information correctly but 3 are reporting: "The TCP output processor has paused the data flow".

After reviewing some of the similar posts, it seems this error message is generic and just says there's nothing wrong with the forwarder, but there's something wrong with the server. 

I reviewed the monitoring console but didn't see anything that would indicate the server or index not having the ability to receive more information. 

Labels (1)
0 Karma

teunlaan
Contributor

Did you check firewall's?  If your forwarder can't connect the indexer, you get the same message

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...