As of lately I've been having this strange issue with one new render node. It's a dual E5-2695V3 (56 threads total).
V-ray spawner is installed as a service (as it is for all the other machines).
On a first render it picks up just fine, but on every next render (same session) it reports "not responding" and after a while it picks up at "Scene loaded, starting render" but it never actually starts the process.
Sometimes it reports no warnings at all, but it still hangs on "Scene loaded, starting render".
The only solution is to restart the spawner service after every render.
This issue is most frequent if I cancel an ongoing render.
Is DR still bound in any way to the Bacburner? This is the only machine that doesn't run backburner server by default.
I cannot find any reason other than that or perhaps the CPU core count for this issue to occur.
V-ray spawner is installed as a service (as it is for all the other machines).
On a first render it picks up just fine, but on every next render (same session) it reports "not responding" and after a while it picks up at "Scene loaded, starting render" but it never actually starts the process.
Sometimes it reports no warnings at all, but it still hangs on "Scene loaded, starting render".
The only solution is to restart the spawner service after every render.
This issue is most frequent if I cancel an ongoing render.
Is DR still bound in any way to the Bacburner? This is the only machine that doesn't run backburner server by default.
I cannot find any reason other than that or perhaps the CPU core count for this issue to occur.
Comment