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!

Dashboards: Hiding charts while search is being executed and other uses for tokens

There are a couple of features of SimpleXML / Classic dashboards that can be used to enhance the user ...

Splunk Observability Cloud's AI Assistant in Action Series: Explaining Metrics and ...

This is the fourth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how ...

Brains, Bytes, and Boston: Learn from the Best at .conf25

When you think of Boston, you might picture colonial charm, world-class universities, or even the crack of a ...