DR nodes idle

[Macker]

Hey guys,

I've noticed that idle nodes (that have just finished rendering something for my colleague) aren't being picked up by my render; they just sit there idling. - and which ones stay idle appears to be at random. One that worked for me 20 minutes ago now doesn't, and so on.

I tried removing them from DR (which shows up in the VRay log as them having been removed) and then adding them again but the vray log shows no sign of them being added again, and they just sit there idling. I then have to cancel my render (which then causes max to crash) and restart it with nothing more than the hope that the nodes will be picked up this time.

Very frustrating.

[ivan.slavchev]

Is the "Restart servers on render end" option enabled? Does this happen only with this particular scene or with all of them?

[Macker]

Yes restart on render end is enabled. I haven't tested on other scenes yet.

[Macker]

I've just tried logging on to each node and restarting the spawners - nothing. Still won't pick them up. Surely newly available nodes let clients know they're available? Or shouldn't the client check every minute or so? I can't see how this would be affected by the scene?

Incidentally I've not had this issue with the old version (3.6) of VRay.

[Macker]

Here's an (apparently) new development...

Kicked off a large (18432 x 1536) render last night, all 3 DR nodes were working on it, along with my workstation. Came in this morning and my local workstation was still working on it, but none of the nodes were - too late to cancel the render and start again...

- Using the DR dialogue whilst it's rendering I removed all the nodes, and then re-added them.
- It seems to have worked, and the nodes joined back in and started rendering the buckets they were assigned.
- After each node completed a bucket it failed to assign a new bucket, as if it's at the end of the render - gradually as more buckets complete the nodes gradually do less and less work as there are no new buckets being allocated.
- Only my local workstation is rendering now. The render nodes have assumed there's nothing more to render???

How do the nodes communicate with the workstations? Surely once a bucket is completed it should ask for the next location of a bucket if one is available?

[tashko.zashev]

I'm testing right now this DR rendering process and the nodes which are ready with the current DR job (Server 1) are automatically taken for the next one (Server 2). This is with V-Ray build "4.02.04.00004" .
Can you give me the exact build you are using ?
This is with Max 2019 right ?

[Macker]

V-Ray 4.02.04.00001 with max 2019

[update] Now despite me re-adding the nodes and them showing up as having been added in the vraylog; they do nothing. I've checked the nodes, the Vray Spawner/Max is running in the task manager, but all are idling with no sign that they're receiving anything.

[tashko.zashev]

Now I see your new post with more information. Maybe it is better to try you scene file here and see what will happen. Do you have time to try this on a basic scene setup?
Still want to see the exact V-Ray version you are using.

[tashko.zashev]

V-Ray 4.02.04.00001 with max 2019

We had DR issues with these builds and they have been replaced with 4.02.04.00004, so please if possible log-in to our web site and download the V-Ray Next for Max 2019 again. Then we can proceed to scene testing if the issue still persist.

[Macker]

As per previous I'm using: V-Ray 4.02.04.00001 with Max 2019

I'll send it over when I get the chance; naturally I now have to wait for this render to complete

Any nodes that I managed to get to join (with buckets) seem to just sit there idling; all their CPU usage is at ~1%. I seem to recall this was an issue with progressive renders previously? After a certain amount of time CPU usage would just drop off to nothing?

see here: https://forums.chaosgroup.com/forum/...93-weird-issue

and https://forums.chaosgroup.com/forum/...usage-on-nodes

[Macker]

I'll give the new build a go when this render is finished and will report back. Thanks Tashko.

[tashko.zashev]

I'll give the new build a go when this render is finished and will report back. Thanks Tashko.

Super, thank you. Waiting for your update!

[Macker]

We had DR issues with these builds and they have been replaced with 4.02.04.00004, so please if possible log-in to our web site and download the V-Ray Next for Max 2019 again. Then we can proceed to scene testing if the issue still persist.

I can't find any mention of DR bugs in the changelog?

[tashko.zashev]

It's not in the change log indeed, not sure if this was forgotten or something else, but will check that out.

[Macker]

Just attaching this to illustrate some more oddities. My local workstation is called "rl-cm-new" and VRay seems to be associating that name with the render nodes IP addresses (10.0.0.214 & 10.0.0.236 & 10.0.0.229)?

Also who/what is 0.0.0.0?

All very odd. Still rendering though *sigh*