thatoneguy
10-13-2005, 09:13 PM
I've run into a snag trying to get a render farm working.
My Network consists of 4 Linux Render Systems
With Hostnames Render1...Render4,
My maya.rayhosts file reads as:
"
RENDER1:7103
RENDER2:7103
"
I can ping Render1 and Render2, They don't have any firewalls up, I *think* I confirmed that Maya Sattelite Service was running on all of them. However whenever I go to Render -> Batch Render, uncheck "Render on this machine". Click Batch Render. The render completes (using my system) and then puts out an error into my render log as follows:
"
10/13/2005
mental ray for Maya 7.0
mental ray: version 3.4.5.2, 06 July 2005
Error: Cannot convert data of type int to type string[].
File read in 0 seconds.
Result: C:/Documents and Settings/gavin/My Documents/maya/projects/default/scenes/HDRIFly__2980.mb
mental ray: got 2 satellite CPUs.
// mental ray for Maya: using rayhosts file C:/Documents and Settings/gavin/My Documents/maya/7.0/prefs//maya.rayhosts
MSG 0.0 error 011329: mi-ray/tcp: not a service (check %SystemRoot%\system32\drivers\etc\services)
MSG 0.0 warn 012219: using fallback inet service 7003
MSG 0.0 warn 012214: bad response: '/usr/aw/mentalraysat34/bin/raysat: error while loa' (144/512)
MSG 0.0 warn 012215: check executable and version used on remote host:port RENDER1:7103
MSG 0.0 error 011213: cannot receive welcome message from host 1 (active)
MSG 0.0 error 011706: cannot add host RENDER1:7103
MSG 0.0 warn 012214: bad response: '/usr/aw/mentalraysat34/bin/raysat: error while loa' (144/512)
MSG 0.0 fatal 011513: SLAVE 1 DIED
MSG 0.0 fatal 011513: SLAVE 1 DIED
MSG 0.0 warn 012215: check executable and version used on remote host:port RENDER2:7103
MSG 0.0 fatal 011513: SLAVE 1 DIED
MSG 0.0 fatal 011513: SLAVE 1 DIED
"
It's not always identical to that, but the general story tends to be the same.
It says that mi-ray/tcp: not a service.
It then proceeds to attempts (I believe) to try Mental Ray Standalone instead. Which it then discovers doesn't exist and kicks back a rejection notice. But I don't understand why the Linux machines are kicking back "mi-ray/tcp: not a service" It is clearly running when I check.
Any and all help would be greatly appreciated.
My Network consists of 4 Linux Render Systems
With Hostnames Render1...Render4,
My maya.rayhosts file reads as:
"
RENDER1:7103
RENDER2:7103
"
I can ping Render1 and Render2, They don't have any firewalls up, I *think* I confirmed that Maya Sattelite Service was running on all of them. However whenever I go to Render -> Batch Render, uncheck "Render on this machine". Click Batch Render. The render completes (using my system) and then puts out an error into my render log as follows:
"
10/13/2005
mental ray for Maya 7.0
mental ray: version 3.4.5.2, 06 July 2005
Error: Cannot convert data of type int to type string[].
File read in 0 seconds.
Result: C:/Documents and Settings/gavin/My Documents/maya/projects/default/scenes/HDRIFly__2980.mb
mental ray: got 2 satellite CPUs.
// mental ray for Maya: using rayhosts file C:/Documents and Settings/gavin/My Documents/maya/7.0/prefs//maya.rayhosts
MSG 0.0 error 011329: mi-ray/tcp: not a service (check %SystemRoot%\system32\drivers\etc\services)
MSG 0.0 warn 012219: using fallback inet service 7003
MSG 0.0 warn 012214: bad response: '/usr/aw/mentalraysat34/bin/raysat: error while loa' (144/512)
MSG 0.0 warn 012215: check executable and version used on remote host:port RENDER1:7103
MSG 0.0 error 011213: cannot receive welcome message from host 1 (active)
MSG 0.0 error 011706: cannot add host RENDER1:7103
MSG 0.0 warn 012214: bad response: '/usr/aw/mentalraysat34/bin/raysat: error while loa' (144/512)
MSG 0.0 fatal 011513: SLAVE 1 DIED
MSG 0.0 fatal 011513: SLAVE 1 DIED
MSG 0.0 warn 012215: check executable and version used on remote host:port RENDER2:7103
MSG 0.0 fatal 011513: SLAVE 1 DIED
MSG 0.0 fatal 011513: SLAVE 1 DIED
"
It's not always identical to that, but the general story tends to be the same.
It says that mi-ray/tcp: not a service.
It then proceeds to attempts (I believe) to try Mental Ray Standalone instead. Which it then discovers doesn't exist and kicks back a rejection notice. But I don't understand why the Linux machines are kicking back "mi-ray/tcp: not a service" It is clearly running when I check.
Any and all help would be greatly appreciated.