Dashboards & Visualizations

Why does Splunk UI search hang or timeout with ResourceNotFound HTTP 404 error?

gesman
Communicator

I've experienced situations where Splunk searches stopped in the middle without any signs of life or progress.
Job -> Inspect Job will show information something along these lines:

ResourceNotFound: [HTTP 404] https://127.0.0.1:8089/services/search/jobs/1413476626.459?message_level=debug; [{'code': None, 'text': 'Unknown sid.', 'type': 'FATAL'}]

Tags (3)
1 Solution

gesman
Communicator

I found the issue is caused by Splunk's default timeout for UI-initiated searches.
To fix it, edit $SPLUNK_HOME/etc/system/local/web.conf by setting reasonably high value (in minutes) for ui_inactivity_timeout, such as:

[settings]
ui_inactivity_timeout = 180

And then restarting Splunk. Above will set timeout value to 3 hours.
See more info here: http://docs.splunk.com/Documentation/Splunk/6.1.4/admin/Webconf

View solution in original post

gesman
Communicator

I found the issue is caused by Splunk's default timeout for UI-initiated searches.
To fix it, edit $SPLUNK_HOME/etc/system/local/web.conf by setting reasonably high value (in minutes) for ui_inactivity_timeout, such as:

[settings]
ui_inactivity_timeout = 180

And then restarting Splunk. Above will set timeout value to 3 hours.
See more info here: http://docs.splunk.com/Documentation/Splunk/6.1.4/admin/Webconf

Get Updates on the Splunk Community!

The OpenTelemetry Certified Associate (OTCA) Exam

What’s this OTCA exam? The Linux Foundation offers the OpenTelemetry Certified Associate (OTCA) credential to ...

From Manual to Agentic: Level Up Your SOC at Cisco Live

Welcome to the Era of the Agentic SOC   Are you tired of being a manual alert responder? The security ...

Splunk Classroom Chronicles: Training Tales and Testimonials (Episode 4)

Welcome back to Splunk Classroom Chronicles, our ongoing series where we shine a light on what really happens ...