We recently upgraded to deadline 7.2, and windows 10 on all computers and now certain computers finish all the frames in an assigned task, but they then hang on 100% and say rendering until manually completed… It seems they never initiate “process exit code 0” they just hang on “wall clock XX rendertime”.
Not sure what could be the problem here:
It clears the memory, unloads all textures, says render complete, but then it will just sit at 100% (rendering)
I let a task just sit on one of the problem computers after completion, and this is the full readout that it does. the job finished in 2hr, but i let it sit until the 5.5hr mark before manually completing the job…
So it looks like any normal job completion, no errors, no warnings. It just never says “process exit code 0” and doesnt requeue the slave for a new job …
any help would be appreciated.
2015-11-16 22:46:06: 0: STDOUT: [2015/Nov/16|22:46:06] V-Ray: Cleaning up bitmap manager
2015-11-16 22:46:06: 0: STDOUT: [2015/Nov/16|22:46:06] V-Ray: Total sequence time 2h 12m 8.7s (7928.7 s)
2015-11-16 22:46:06: 0: STDOUT: [2015/Nov/16|22:46:06] V-Ray: Render complete
2015-11-16 22:46:06: 0: STDOUT: [2015/Nov/16|22:46:06] V-Ray: ========================
2015-11-16 22:46:06: 0: STDOUT: [2015/Nov/16|22:46:06] V-Ray: Clearing exporter memory...
2015-11-16 22:46:06: 0: STDOUT: [2015/Nov/16|22:46:06] V-Ray: Total time clearing exporter memory 0h 0m 0.0s (0.0 s)
2015-11-16 22:46:06: 0: STDOUT: Scene XX completed.
2015-11-16 22:46:06: 0: STDOUT: Shave shaders for Vray unloaded.
2015-11-16 22:46:06: 0: STDOUT: Shave shaders for Vray unloaded.
2015-11-16 23:18:53: Skipping thermal shutdown check because it is not required at this time
2015-11-16 23:42:42: Skipping thermal shutdown check because it is not required at this time
2015-11-16 23:54:39: Skipping thermal shutdown check because it is not required at this time
Hi,
Could you post the full slave log from the moment the slave picks up the job, to put this into better context? Feel free to email the contents to support@thinkboxsoftware.com to generate a private support ticket if required. If you do this, please reference this forum post. When you mentioned that:
is it possible that there is a pattern here on your machines? ie: only one or 2 of your machines are missing a certain shave shader configuration/plugin/access permission?
If you execute the same render at the command line outside of Deadline on one of these troublesome machines does it complete everytime ok? If so, could you also provide the Stdout (log) of this successful render, so we might compare the 2 logs and see if anything stands out?
We’ve currently got exactly the same thing happening on Windows 7 machines when rendering Cinema4D jobs, Max and After Effects don’t seem to be affected.
However we don’t have any machines that render the tasks normally, every one I have tried up to now just site there at 100%.
It’s a bit of a long-shot, but have you tried disabling firewall and anti-virus software? Anti-virus software in particular can cause unusual delays. If you have ruled those out, I would suggest setting up a remote session with our support team by creating a support ticket.
Antivirus and Firewall don’t exist on the render slaves, so we can pretty much rule that out.
What I have found out is that standard C4D jobs don’t have the problem, but we have 25 machines that also have X-Particles (x-particles.com), and jobs using X-Particles are the ones that just stay on 100% without ending the task.
…