Monitoring Splunk

500 -Splunk Daemon is not responding:

kmaynard616
Engager

I am getting this error when I load some of my dashboards:

500 -Splunk Daemon is not responding:([Errno 73] Connection reset by peer

It seems to do it when my dashboards have searches that go back 3 or more days. I was wondering if anyone could help me in figuring out why this error keeps occuring.

Tags (1)
0 Karma

jgedeon120
Contributor

Sounds like your system is being overloaded when the dashboard is loaded. If the install is on linux you can look to see how many searches are running, ps -ax | grep splunkd, also the top command will show you any load that is going on.

Another search I would also check your metrics.log for any blocked queues. Search for "blocked=true"

0 Karma

zacshaik
New Member

I am also seeing error "500 Splunkd daemon is not responding (The read operation timed out)" when search is running and times out? running Splunk version 4.3

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!

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...