vray spawner not responding on boot or when using light cache map file

[francomanko]

So I'm trying another test to see why my DR are slow using the local machine and have come across another problem.

If i register vray as a service on my renderfarm machines, then when i do a DR render using a lightcache or irradiance file I get

// Warning: line 1: V-Ray : Render host render01 (192.168.20.2:20207) is not responding //

however if I reinstall vray but this time don't register as a service but instead start it using the 'launch vray render slave' it works just fine.

Also, if i reboot my machine (with vray registered service) even thought the vrayspawner service says its started, it wont respond when i render, i have to stop it then restart it, then it works.

All machines are using latest official vray 3.40.03, windows 7 pro and they can all access the lightcache files etc.

thanks

[vlado]

What Windows user is the service running as?

Best regards,
Vlado

[francomanko]

Im not totally sure how i find that, but the only user account that's logged in has administrator rights if that's the info you are wanting?

[Svetlozar Draganov]

Im not totally sure how i find that, but the only user account that's logged in has administrator rights if that's the info you are wanting?

Go to Services, find V-Ray DR Spawner service, open its properties and then check the Log On tab:
(note that this is a screenshot from VRLService, not V-Ray DR Spawner)

The logged user account is not relevant to the service, so even though the logged account has administrative privileges V-Ray Spawner service won't if it logged with Local System account or other account that is not administrative.

[duaxiong]

I'm having this same issue; three machines, two slaves. Both slaves are nearly identical, running Windows 7 Pro.

One slave works as expected, but the other will not respond after boot up. When I check, I can see that the spawner is running and vray.exe is running, both as SYSTEM, but it does not respond to any render requests.

If I shut down the spawner and vray.exe once and then restart the spawner or Launch V-ray Render Slave manually, it works fine.

There are some minor differences between the two slaves: the working slave has Maya installed and two different versions of the spawner 2017 and 2018 running concurrently. The troubled slave has no Maya and only one spawner 2018...but these differences should not matter, should it?

[ivan.slavchev]

I'm having this same issue; three machines, two slaves. Both slaves are nearly identical, running Windows 7 Pro.

One slave works as expected, but the other will not respond after boot up. When I check, I can see that the spawner is running and vray.exe is running, both as SYSTEM, but it does not respond to any render requests.

If I shut down the spawner and vray.exe once and then restart the spawner or Launch V-ray Render Slave manually, it works fine.

There are some minor differences between the two slaves: the working slave has Maya installed and two different versions of the spawner 2017 and 2018 running concurrently. The troubled slave has no Maya and only one spawner 2018...but these differences should not matter, should it?

Does this behaviour changes if you register the service with a normal account, rather than using the Local system one.
Also - having 2 V-Ray for Maya spawners at the same time is a bad practice, unless they use different ports. Having any 2 processes fighting for a port is not a good idea and can lead to unnecessary netwrok load. YOu can either stop / start the one you need or just use different ports so each process will be able to open a different socket.