Monitoring Splunk

Tcpout Processor: The TCP output processor has paused the data flow. Forwarding to output group production has been blocked for 10 seconds

ankitcharolia09
Engager

I use Splunk Enterprise 6.6.1
I see this warning message in my splunk master node.

"Tcpout Processor: The TCP output processor has paused the data flow. Forwarding to output group production has been blocked for 10 seconds. This will probably stall the data flow towards indexing and other network outputs. Review the receiving system's health in the Splunk Monitoring Console. It is probably not accepting data."

Please help me to fix this problem.

Thank you

Tags (1)
1 Solution

bpenn_splunk
Splunk Employee
Splunk Employee

Check to make sure that you don't have an outputs.conf in your /etc/system directory as that was the issue when I had this problem.

View solution in original post

bpenn_splunk
Splunk Employee
Splunk Employee

Check to make sure that you don't have an outputs.conf in your /etc/system directory as that was the issue when I had this problem.

View solution in original post

lmorillogonzazl
Explorer

Hi, I solved the problem, at the time of indicating the name of the forwarder I put the ip of the receiver and with it fixed my problem

0 Karma

lmorillogonzazl
Explorer

I have the same problem, has someone solved it? could you help me with this problem?

p_gurav
Champion

Try this

1) check indexers have enough space.
2) check Licesnse should not cross daily limit.

Also can you provide your configuration file details?

0 Karma

bpenn_splunk
Splunk Employee
Splunk Employee

Check to make sure that you don't have an outputs.conf in your /etc/system directory on your Indexers as that was the issue when I had this problem.

0 Karma

jonasm1
Explorer

I have the same issue: Tcpout Processor: The TCP output processor has paused the data flow. Forwarding to output group cprobe has been blocked for 10 seconds. This will probably stall the data flow towards indexing and other network outputs. Any suggestions?

0 Karma
Register for .conf21 Now! Go Vegas or Go Virtual!

How will you .conf21? You decide! Go in-person in Las Vegas, 10/18-10/21, or go online with .conf21 Virtual, 10/19-10/20.