Getting Data In

unable to search index="_internal" for heavy forwarder instance from search head console but splunkd.log is functional

Hemnaath
Motivator

Hi All, Suddenly I am unable to search the index="_internal" for all heavy forwarder instance from search head console. When checked in the splunk HF instances, could see /opt/splunk/etc/var/log/splunk/splunkd.log are getting updated but the same is not able to searched via splunk console.

I could see this message getting popped out in HF console .

"Tcpout Processor: The TCP output processor has paused the data flow. Forwarding to output group all_indexers 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"

Kindly guide me how to troubleshoot this issue.

0 Karma
1 Solution

Hemnaath
Motivator

Hi somesoni2, thanks for your effort, I hope the issue got fixed, we are able to search the index="_internal" for all heavy forwarder instance from search head console.

After restarting the splunk service the issue is fixed.

thanks for your effort.

View solution in original post

0 Karma

Hemnaath
Motivator

Hi somesoni2, thanks for your effort, I hope the issue got fixed, we are able to search the index="_internal" for all heavy forwarder instance from search head console.

After restarting the splunk service the issue is fixed.

thanks for your effort.

0 Karma

Hemnaath
Motivator

Hi All, Can any one guide me on this issue.
thanks in advance.

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...