Windows 10 and renderfarms

[ricoholmes]

Hello,
Having a lot of problems here with rendering on our farm, but only on the nodes with windows 10. I can render a decent amount of frames (often hundreds), but at some point the windows 10 clients disconnect. This usually means that overnight, or guaranteed over weekend renders the machines will have dropped off the farm by the time I return. Now, this may well not be a VRay problem (I actually doubt it's VRay, but the fact that the VFB doesn't always autoclose makes me wonder. it feels sometimes like Vray isn't "releasing" the scene/image/vfb and the renderpal clients then eventually close due to timeout.)

Importantly: It may well be RenderPal at fault, which is why I'm just checking here to see if anyone else has experienced similar problems with Deadline, Smedge etc before I point the finger at RenderPal ?
Has anyone else experienced this issue ?

The other nodes, all windows 7, run flawlessly. They also continue happily when all the Win 10 nodes have disconnected

Vray: Build 26501, windows 10 nodes fully up-to.date.

[Morbid Angel]

I haven't used win10, but I recall we had an issue with deadline on win7 where one slave would drop after a certain period. It turned out it was on a different time zone and wouldn't respond to repository in time and deadline will think it stalled and kill it.

[ricoholmes]

Ah that wasnt the problem, but a good one to keep in mind. I did log into the studio to check though

[Morbid Angel]

yeah I didn't think it would be. Might want to try a render using backburner to rule out any render manager related things...

[vlado]

If you look at the V-Ray log file on those slaves when they are in such a state, does it say anything useful?

Best regards,
Vlado

[ricoholmes]

I'll try to catch it "in the act" as such Vlado. I'd estimate it only crashes/stops post render maybe 1-2% of the time, and as it's a remote session for those nodes it's rarely on-screen when it happens.
Will also try backburner sessions when I get an opportunity (though with current project deadlines "opportunity" looks like "in the new year")

[svetlozar.draganov]

We have some doubts that this might be a bug since we have similar issue(it happens on win7 as well) into our environment with 3.30.xx builds.
Is there any chance to switch back to version 3.20.03(or a nightly build 3.25.01) and see if this issue is still there?

[ricoholmes]

Sorry for the delayed response. Wanted to be sure before reporting back. It's been running a day and a half on 3.25.01 nightly and no sign of it hanging any of the Win10 nodes as yet.

[svetlozar.draganov]

Thank you very much for the feedback - that confirms our doubts for the bug in 3.30.xx, we'll have to investigate what's going on.
Please keep us posted if any change occurs.