ecFlow's documentation is now on readthedocs!

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

When zombies occur, it is not always easy to reason why they have occurred, and also which machine is giving rise to them

In ecflow 5.0.0 this has been improved.  Now when zombies appear in the GUI dialog, it will be accompanied with an explanation.

Additionally we also try to show the host where the zombie process is residing

Here is an example of the possible reason why.

  •  process id miss-match, password matches. Job scheduled twice. Check submitter
  • Both PID and password miss-match. Re-queue & submit of active job?
  • Password miss-match, PID matches, system has re-cycled PID or hacked job file?
  • Two init commands or task complete or aborted but receives another child command
  • Created by user action, In this case we will actually list the offending user command.  [ force | delete | begin | re-queue | execute (i.e. rerunning an already active job), etc ]
  • Task not found. Nodes replaced whilst jobs were running

     


  

  • No labels