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.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...