I’m posting this in a new thread, even though I started it in other places, but I thought it warranted it’s own topic. I have searched this topic, high and low, and tried everything. Most of the thread were unresolved, and none worked for me
When I render a scene, low resolution with low setting, it works fine using DR. When I increase the settings, and the resolution, the slaves do not participate in the render. All my slaves get the scene transferred, but nothing ever happens. The below image shows where my V-Ray message window sits, and does nothing from there. All my slaves are running 90% ram, and 25% CPU, so something is happening.
they never join, even when the render time on the main PC is hours. I can render 8.5 x 11 @ 300dpi without an issue. When I try to render out higher, it’ll get stuck. I did get a virtual memory error on one of the slaves, but that shouldn’t’ hold everything up, should it?
One of my slaves stopped responding, which seems to have been holding all the other slaves up. Is this normal? All of a sudden my PSD-Manager stopped responding, which was on slave 1. Slave 1 was up and running, I could ping it, but V-Ray said it wasn’t responding, and so did PSD Manager. I un-plugged the network cable, running to slave one, and plugged it back it. Now everything seems to be working.
I’m still fighting this thing. What does this mean? It’s from one of my slaves:192.168.8.101 is my license server, and my main workstation.
[2012/A/6|11:34:12] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|11:37:54] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|11:39:23] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|11:44:27] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|11:47:24] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|11:48:12] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|11:50:07] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|11:52:12] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|13:09:31] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|14:58:49] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
[2012/A/6|15:21:19] warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0
I think I solved my madness. With a little troubleshooting 101, I realized when my issues started. I installed Uniblue on three machines, and those 3 machines were the ones causing me a headache. Now, having said that, why does one bad apple spoil the bunch? When one slave was having issues it seemed to have hung up everything else. When I killed the problem slave the other slaves would work, but if I didn’t kill the task, then the other slaves went on some kind of server strike.
I do have identical versions, and restart on end is checked. I think things are running good now, but I will not know until I send another one, which will be later today[quote=“joconnell, post:8, topic:39083, username:joconnell”]
Make sure you have identical V-Ray versions on all machines.
Also we will advise you to use “restart slave on render end” option as well.
[/quote]
I keep them all updated, but I will sure check.[quote=“Neilg, post:2, topic:39095, username:Neilg”]
check your window updates on all machines bobby and see if it helps
[/quote]
1. turn off all the firewalls
2. run the slaves manually not as a service
3. try the 2012.1 backburner if you havent already
4. check the vray licences setup on the slaves machines (i write computer names there)
i have to say though we had some bad issues lately with BB and new vrey especially when connected with newest version of Multiscatter where you have to install both C++ libraries etc…nasty thing.
Today i got another ugly bug with BB so we decided to move to 2012.1 version which seems to run fine now
as far as i remember, sometimes windows updates can screw up your whole DR setup and you have reset all the FW setup…stupid thing
firewall is off, but it is strange that when I ran BB, one of the slaves showed a blocked dialog (I unblocked). I ran a small job using backburner, and it ran fine. Everything is looking good, so far.
it must have been the wonderfull Windows update that messed aroud with your FW settings.
We update only from time to time…and have the automatic update function turned off…onl yfor this particular reason
glad it works!
