Join the Conversation
- Find Answers
- :
- Using Splunk
- :
- Splunk Search
- :
- Re: Read time out while opening Job manager in Spl...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Read time out while opening Job manager in Splunk UI
Hi,
I am getting the below error while opening Job manager in splunk UI.
[JobManager module] Splunkd daemon is not responding: ('The read operation timed out',)
It will be very helpful if anyone can suggest me how to avoid this error.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have seen this happening when there is a high count of jobs in dispatch. If you are able to, run clean dispatch command to delete jobs older than X days or X hours (choose a number for the days or hours)
If you're in a pinch, delete everything in the dispatch directory but be aware that you may have some artifacts used by dashboards or saved by users that will be deleted. The search can always run again but that might not be ideal.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think this occurs because a search head in the pool is down.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue
6.0.3, utilizing search head pooling
[JobManager module] Splunkd daemon is not responding: ('Error connecting to /services/search/jobs: The read operation timed out',)
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the exact same issue, I am using search head pooling and everything else seems to be working properly, when I ping the NFS where the job dispatch directory is, I see approx 1 ms of latency, the RAID1 drives are rated together to give me over 12000 IOPS
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
this was supposed to be a comment, not an answer, sorry about that.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can anyone help??
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
[Puzzles] Solve, Learn, Repeat: Matching cron expressions
Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass
May 2026 Splunk Expert Sessions: Security & Observability
