Hi,
As Nuke processes a job via deadline slave, if for any reason the task fails, then deadline slave will auto-recover and potentially another slave will pick the task/job up and attempt to process it as per normal deadline procedure.
However, whenever Nuke processes it always temporarily creates a “*.tmp” file which can sometimes NOT get deleted during a job/task crash, so Deadline slave is then unable to proceed to process it via Nuke. This is separate from the final output image that is created by Nuke by effectively “removing” the “.tmp” part of the image file and hence returning the final image.
So, what would be most useful, because anyone running windows based file servers/XP OS workstations would have noticed (as this problem seems to happen more frequently for them), is for Deadline to have the ability in the Nuke plugin to automatically attempt to delete the particular frame “.tmp” file IF IT EXISTS in the relevant output directory of that particular Nuke write node BEFORE the Nuke via Deadline slave attempts to process it. Returning any error message such as access denied/file locked to another process/task failed via a error report would also be most useful.
Hopefully, this makes sense!
Thanks,
Mike
Hi Mike,
What happens when another slave goes to render a frame and the *.tmp file already exists? Do you get an “access denied” error? Does the *.tmp file always cause problems if it already exists? I’m just trying to get more familiar with the problem.
Thanks!
- Ryan
I will submit a support ticket with an example error report.
Mike