NetRender still ready and waiting

tbrucebowers wrote on 2/20/2005, 11:29 PM
OK, I've tried everything, and my host master says I've got two renderers "ready", but they never render a frame. The local master renders fine, but the network renderers just sit there being "ready"

I have checked my file paths using the command line, both looking in from the renderers across the network and locally on the render server all files and folders show up fine.

One of my renderers is on a seperate machine on the network and one is the second processesor on the local machine, both refuse to render.

The local Network Render Service is version 5.0.0.160
The network machine is version 5.0.0.134

BUT, I'll repeat again, both refuse to render and show as "ready" I assume if it were a version problem the local 160 version would work and the network 134 version would not.

How do I get this to actually work. I have read every post on this issue and everything posted by Sony. What am I doing wrong?

Comments

Liam_Vegas wrote on 2/20/2005, 11:33 PM
You do select "distribute render" when you initiate the network render right?
tbrucebowers wrote on 2/21/2005, 1:26 AM
Yup,

I just updated everybody to 5d and one of the networked machines just kicked in. The host stills shows it as "ready" not "busy" or "working" or anything else informative, but it is never the less cranking out frames. I'm going to fire up the second processor on the local host and see if it will work. I'll keep you posted.

Got any tips on how to make the launching of a second iteration of NetRenderService a little less painfull than sticking my face into the toothy slobbering maw of the command line?
tbrucebowers wrote on 2/21/2005, 2:02 AM
Okay, Yahoo!

The update to 5d (build 194) did the trick.

I had one machine with a wonky serial number, but once I reset that, I have the host and two servers working great!

Now, someone want to tell me an easy way to launch that second processor on my host machine. The command line routine is a bit much for something that gets done many times a day.

Liam_Vegas wrote on 2/21/2005, 2:06 AM
The only time I found that it would not work (even though it says ready) is where the Veg file I was using was referencing a media clip that was not accessible via the share. The local renderer could see it... but the remote ones could not.

The remote renderers would show they got the message to start up their render session... but would then fail with an error message. I think if you open the actual log file on the remote render box you can see further detailed information on the error.

As for setting up the 2nd renderer on your dual processor. You should be able to create a shortcut for the 2nd rendered with the parameter you need to tell it which port to run on... then it's just a matter of launching that shortcut rather than manually messing with the command line every time.
tbrucebowers wrote on 2/21/2005, 8:53 AM
Hi Liam,

Everything is working fine. The upgrade to Vegas 5d build 194 solved everything.

Regarding the second iteration of Network Rendering Service; the hard part for me is that I don't really understand what's going on in the command line. From what I can see it is launching a second iteration of Network Render Service with a second config file, but still the same exe file. I don't have the chops to create a shortcut to do that. I assume there is a simple way to just write out the command line sequence and then make it into some sort of executable, but once again beyond my chops.

Anybody? Or do I have to go out and get "DOS for Dummies"?