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!

Splunk Edge Processor | Popular Use Cases to Get Started with Edge Processor

Splunk Edge Processor offers more efficient, flexible data transformation – helping you reduce noise, control ...

Introducing New Splunkbase Governance!

Splunk apps are essential for maximizing the value of your Splunk Experience. Whether you’re using the default ...

3 Ways to Make OpenTelemetry Even Better

My role as an Observability Specialist at Splunk provides me with the opportunity to work with customers of ...