What causes a dead job alert and How to trace a dead job alert

Question

Question

ED Coder · Apr 14, 2020

DeadJobAlert: Job 'X478915' for config item 'Business Service' was marked as 'dead' under ghost Id 'sys:ZX478915_6117'

This is the error message I get, but can you advice how can I start debugging this? I look at the jobs and I just see "dead" I cant see any information on the message itself.

I would appreciate if you could advice on how to start debugging such a job. Events are also non-informative.

Discussion (3)2

Log in or sign up to continue

Erik Hemdal · May 27, 2020

Eric, your best bet is to investigate at operating-system level; a dead job means it's no longer around as far as can be detected within Ensemble. As to what to check, this depends very much on the specific OS platform you're running; different ones have different tools.

For Linux, try looking in /var/log/messages. For Windows, the Event Viewer is where to go. And there may be useful information in the Caché cconsole.log.

The WRC can help you with getting to the bottom of problems like these because there are many reasons why a job might die unexpectedly.

Erik

0 0

score 0 · Answer 1 · 2020-04-14T09:19:52-04:00

Hello Eric,

This message indicates that an Ensemble job had unexpectedly terminated. I would recommend checking OS logs or looking for other events that could have triggered a process termination outside of Ensemble.

score 0 · Answer 2 · 2020-04-15T03:33:05-04:00

Thank you for responding to my question Vic. Ok, thats a start, I will check the events and see if there is anything causing the dead jobs.