Automatic node updating questions

[Travis Serio_cg]

I am curious about the process of network nodes updating their v-ray versions.

Currently I have 3.6 on 1 machine and as I toggle swarm I see other nodes which are version 3.4 are starting to update to 3.6 on their own. This would be great except once they switch to 3.6 they flip over to UNSTABLE in the swarm list and then say they can't retrieve a license...

Can I turn this updating off? I am not sure that I want to endanger the render boxes on my network that are working and stable until I vet 3.6 better.

[Travis Serio_cg]

ok it appears after a node restart the nodes go back to their 3.4 versions. Any info on how this works, would be great.

[ivan.slavchev]

The idea of changing versions is that SWARM detects the version used on the workstation machine (that you submit the render job from) and uses the same V-Ray build on the render nodes. When you install a new V-Ray version SWARM first transfer the V-Ray build from the main workstation onto the nodes before it starts rendering.
You can see all version you have on your render nodes by navigating to http://IP_Address:24267/vray-versions, where IP_Address is the IP address of the specific render node.

This shouldn't experience a license issue, though - did you check if your license server is functioning correctly? You can navigate to http://localhost:30304 on the license server machine and check if you can see your licenses.
You can also check the license settings on the computers themselves - https://docs.chaosgroup.com/display/...ration-License

If you change some options on a particular node - you can just copy its configuration onto the other nodes instead of manually configuring every computer using the "Copy configuration" option - https://docs.chaosgroup.com/display/...orking-Network

I'd recommend using the latest SWARM build on all nodes - you can use ver. 1.4.3 that's included in V-Ray 3.6 for Rhino installer.

[Travis Serio_cg]

Thanks Ivan!