Manual
When zombie s arise they can be handled manually by ecflowview. (See Zombie) or via the command line interface:
...
ecflow_client –zombie_adopt <task-path>, will not allow this, due to the potential for data corruption.
In this case the normal behaviour would be kill both process, and re-queue the task.
In the extreme, we can by pass the authentication. (i.e allowing the request to be handled by the server).
This SHOULD only be done when user is you are sure they handle the zombie and they do not has been killed, and you don’t want to re-queue the job.
...
After the job has completed, be sure to delete this variable. Otherwise if zombies arise again, there is a considerable risk of data corruption.
Automated
It is also possible to ask ecflow_server to make the same response in an automated fashion. How ever very careful consideration should be made before doing this. Otherwise it could mask a serious underlying problem.
...
ecflow_client --alter add zombie "ecf:adopt:complete:" /suiteZ
Semi-Automated
Sometimes zombies can arise for more obscure reasons. i.e The job sends a --init message to the server, meanwhile the server is busy(i.e processing jobs), when finally the server makes the task active, and sends a message back to the client/job the ecflow_client has timed out. This causes the ecflow_client to send the same message again. However this time the server treats the child command as a zombie, since the task is already active. Hence we get these false zombies.
...