DR not working on some nodes: Disconnected by client / Currently busy

V-Ray V-Ray for 3ds Max Issues
1

Hi,
I’ve got an issue with some DR nodes which sometimes do not join in.
In the Vray log window it says:
warning: Render host […] disconnected by client
warning: Server […] is currently busy

Restart on render end is checked but doesn’t help.
Restarting the Vrayspawner manually fixes the issue but only for some time until the error appears again.

It seems that a random amount of DR nodes is affected, but not all of them together. Some nodes render perfectly but may disconnect when rendering another scene.
All render nodes are identically configured and run Vray Next 4.30.01
(See Vraylog below.)
I’ve seen other threads regarding this error but could not find a solution.

Any hints how to solve the issue?
Thanks

[2020/Feb/17|23:49:53] ============================================================
[2020/Feb/17|23:49:53] Console created, V-Ray 4.30.01 for x64 from Dec 18 2019, 13:46:39
[2020/Feb/17|23:49:53] ============================================================
[2020/Feb/17|23:49:53] Compiled with Microsoft Visual C++ compiler, version 19.12
[2020/Feb/17|23:49:53] Host is 3ds Max, version 21
[2020/Feb/17|23:49:53] V-Ray DLL version is 4.30.01
[2020/Feb/17|23:49:53] Using folder “C:\Users\RENDER~1\AppData\Local\Temp\vray_assets_cache” for caching assets for DR.
[2020/Feb/17|23:49:53] Using file “C:\Users\RENDER~1\AppData\Local\Temp\vray_assets_cache/cache_info_20204.txt” for storing assets cache information.
[2020/Feb/17|23:51:49] Received TM_GET_CAPABILITIES from 192.168.88.76
[2020/Feb/17|23:51:54] Received TM_START_RENDER from 192.168.88.76
[2020/Feb/17|23:51:54]
[2020/Feb/17|23:51:54] Starting DR session from 192.168.88.76
[2020/Feb/18|00:09:19] Received TM_GET_CAPABILITIES from 192.168.88.76
[2020/Feb/18|00:09:24] Received TM_START_RENDER from 192.168.88.76
[2020/Feb/18|00:09:24] warning: DR request received from 192.168.88.76, but currently busy with 0.0.0.0
[2020/Feb/18|00:13:57] Received TM_GET_CAPABILITIES from 192.168.88.76
[2020/Feb/18|00:14:02] Received TM_START_RENDER from 192.168.88.76
[2020/Feb/18|00:14:02] warning: DR request received from 192.168.88.76, but currently busy with 0.0.0.0

2

Hasn’t anyone got an idea? Am I the only one with this issue?

Thanks

3

Do you have “restart servers on render end” option enabled in DR settings? If not - try it, it’s meant to restart slaves after a job is finished, so that suck nodes are freed.

4

Yes, restart servers on render end is enabled but doesn’t help.

5

The problem persists and it’s quite frustrating to have to manually restart vrayspawner several times a day.
Isn’t there any solution?

screenshot_vray_messages.jpg
screenshot_vray_messages.jpg423×315 51.3 KB

6

I have the same problem for a long time and I wasn’t able to solve it :frowning:

7

Can you message us at support@chaosgroup.com (please include a link to this topic)?
It’s probably something related to the specific setup, so it’ll be best if we can look into it via the ticketing.

8

Having same issues since Win10 update maybe? I suspect it is windows network or permissions? I restart and restart slaves. Eventually they work for 1 or 2 renders, then the trouble starts again.
I get “busy”, “can’t connect”, etc.
Currently, node is still working, but “failed to receive irradiance map(3)” - on a node that just rendered the previous image.

*or they are just unreachable and don’t resolve in the server window.

9

I have also noticed a increase in nodes disconnecting and not helping out in DR the last couple of weeks.

I have opened a case with support today.

10

Running the spawner as a service seems to have helped. It was something about the user profile that was running the spawner program. I’m not sure if this 100% fixed the problem but there are a lot fewer errors - from the same user profile.