https://community.splunk.com/t5/Getting-Data-In/The-TCP-output-processor-has-paused-the-data-flow/m-p/530166#M89263 <P>Did you check firewall's?&nbsp; If your forwarder can't connect the indexer, you get the same message</P> Fri, 20 Nov 2020 08:39:20 GMT teunlaan 2020-11-20T08:39:20Z https://community.splunk.com/t5/Getting-Data-In/The-TCP-output-processor-has-paused-the-data-flow/m-p/529567#M89210 <P>I recently transitioned to a new instance of Splunk and have been having some trouble configuring the new environment.&nbsp;</P><P>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".</P><P>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.&nbsp;</P><P>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.&nbsp;</P> Mon, 16 Nov 2020 16:13:29 GMT https://community.splunk.com/t5/Getting-Data-In/The-TCP-output-processor-has-paused-the-data-flow/m-p/529567#M89210 Wierengaaj 2020-11-16T16:13:29Z https://community.splunk.com/t5/Getting-Data-In/The-TCP-output-processor-has-paused-the-data-flow/m-p/530166#M89263 <P>Did you check firewall's?&nbsp; If your forwarder can't connect the indexer, you get the same message</P> Fri, 20 Nov 2020 08:39:20 GMT https://community.splunk.com/t5/Getting-Data-In/The-TCP-output-processor-has-paused-the-data-flow/m-p/530166#M89263 teunlaan 2020-11-20T08:39:20Z