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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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 ...