...
When zombie s arise they can be handled manually by ecflow_ui. (See Zombie) or via the command line interface:
| Code Block | ||||
|---|---|---|---|---|
| ||||
ecflow_client –-zombie_get # This will list all the zombies in the server.
ecflow_client --zombie_kill=<task-path> # Ask the server kill the zombie process. Use ECF_KILL_CMD
ecflow_client –-zombie_fail=<task-path> # Ask the zombie to fail. This may result in another zombie because abort child command in the job, will be called.
ecflow_client –-zombie_fob=<task-path> # Used to unblock the child, allows the job to proceed. However this will only work for zombies where the password does not match.
ecflow_client –-zombie_adopt=<task-path> # Copies the password stored on the zombie onto the task. Allows the job to proceed, and update the state in the server
# ( i.e. due to init,complete,abort).
# It is up to the user, to ensure that the zombie has been dealt with before doing this.
ecflow_client –-zombie_remove=<task-path> # Remove the zombie representation in the server. Typically this is done, when we are sure we have handled the zombie.
# The zombie will re-appear next time it communicates with server, if this is not the case.
ecflow_client –-zombie_block =<task-path> # Ask the jobs to block at the child command in the job. Prevents the job from proceeding.
# (This is the default behaviour for the init, complete and abort child commands)
|
...
Sometimes we may want the job to proceed but "ecflow_client –zombie_adopt=<task-path>" does not work. i.e. we have the case where zombies password matches, but the process id (ECF_RID) are different.
...