Strange spawner process problem.

[cadmonkey33]

Hello,

We're having a very odd problem with our DR setup. Some of our slaves are ending up with multiple vrayspawner2013 processes running, and we're ending up with 6+ 3dsmax.exe processes running. Once they get in this state they stop responding to DR.
Our setup doesn't use the spawner processes, it uses the services, so we're not sure what is launching the vrayspawner2013 processes.
Also, bizarrely, this seems to be happening when rendering with vray3 which shouldn't even use vrayspawner2013.

Our setup is Max2014 with Vray 2.5 and Max2015 with Vray 3.10 on all pc's. We run the vrayspawner2013 and vrayspawner2015 services on all pc's.

I've never seen the issue with the vrayspawner2013 process being launched before we installed vray3. Maybe there is some confusion going on between versions.

kind regards,
Nat.

[cadmonkey33]

After playing around a bit, this seems to be related to the 'restart servers on render end' feature. It looks like it's closing the service(maybe) and running the process instead, though it seems to be affecting vray 2's spawner, and we're sometimes ending up with multiple processes running.

Edit: Well, switching off 'restart servers on render end' has fixed my problem, which is fine since I have my own way of restarting slave services, but there is definitely something odd going on with that option.

[Svetlozar Draganov]

This might happen if both V-Ray Spawners are listening on the same port simultaneously.
Are the V-Ray Spawners started manually or as a windows service?
Have you changed the default port number on at least one of them?

[cadmonkey33]

Ahah. Thats makes sense.
I've used the VRAY_DR_CONTROLPORT environment variable to change the port for vray 3 and so far it's behaving.

Thanks for the help.
Nat.