Monitoring Splunk

Error message

sahils
New Member

I am getting below error message.

Forwarding to indexer group primary_indexers blocked for 100 seconds.

Can you please explain why this error message is coming and is there any impact on application.

Thanks,
Sahil

Tags (1)
0 Karma

Raghav2384
Motivator

Hello,

Looks like it is not able to communicate to the set of indexers you've pointed it to. See if the target Indexer/Splunk instance is up and running.

Do a telnet to target indexer.

telnet ipaddress 9997 and also look at splunkd.log for any TcpInputProc errors. Hope this helps!

Thanks,
Raghav

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

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...