Monitoring Splunk

Splunk Indexer Error

abhijitnath89ax
Loves-to-Learn

We received the below error in splunkd.log on our indexer server. We are using cluster env with 6 indexers. The indexers are coming up and down

11-05-2020 07:43:17.734 +0000 WARN TcpInputProc - Stopping all listening ports. Queues blocked for more than 300 seconds
11-05-2020 07:43:17.734 +0000 INFO TcpInputProc - Stopping IPv4 port 9995
11-05-2020 07:43:17.734 +0000 INFO TcpInputProc - Stopping IPv4 port 9997
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Why are the queues blocked?  Use the Monitoring Console to see which queue is blocked then address it.  Usually, a slow storage system is the cause.

---
If this reply helps you, Karma would be appreciated.
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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...