Splunk Search

[EventsViewer module] Cannot access search data; job <job_id> is a zombie and is no longer with us

the_wolverine
Champion

I recently restarted Splunk and found that a bunch of jobs return this error when I click on the jobs link. What happened to those jobs?

Tags (3)
1 Solution

the_wolverine
Champion

Splunk's current behavior is that it does not keep track of paused or backgrounded searches after a restart.

View solution in original post

the_wolverine
Champion

Splunk's current behavior is that it does not keep track of paused or backgrounded searches after a restart.

the_wolverine
Champion

Currently, all child processes die when splunkd goes down. So, no searches will surviv a restart. Please file an ER and provide your usecase if you need this in a future release.

0 Karma

Dan
Splunk Employee
Splunk Employee

What about jobs that were active? Do any searches survive restart?

0 Karma

the_wolverine
Champion

And I talk to myself.

Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...