Troubleshoot Network rendering with mental ray for Maya

Why can’t I install the rayserver service or edit the services file?

Ensure you have administrator (or root) privileges on the machine.

I have everything correctly set up, but I still can't network render.

Here are various possibilities to check.

Port number

One possibility is that the network port number you are using is already being used by another service. Ensure that there is no other entry in the services file that is using port 39010 (mental ray standalone) or port 7412 (mental ray for Maya Satellite). If that port number is already taken, you need to pick a new available port number and use that same number for all master and slave machines that are to work together.

You may need to change the port number.

To do so on Linux and WIndows, edit the port services file located at:

(Linux) /etc/services
(Windows XP) C:\Windows\system32\drivers\etc\services

To do so on Mac OS X:

(Mac OS X) Open NetInfo manager (/Applications/Utilities/NetInfo Manager) and navigate to /services; then change the port number of the mental ray or mental ray for Maya satellite service.

In the services file, ensure that the following line exists:

mental ray standalone 3.9.1: mayamr391 39010
Note
The actual service may have a different name. Please check your services file.
mental ray for Maya Satellite 2012: mi-raysat2012 7412

where 7412 or 39010 is the port number. Make sure the port number is the same on the master machine and all slave machines.

Licensing of mental ray standalone

(mental ray standalone) You may need to edit a file called the rayd file located in the mental ray 3.9.1 installation bin directory. Fill in the name of your SPM License server and uncomment the setenv SPM_HOST line.

Restarting the service (Windows)

To restart the server on Windows, go to mental ray bin directory and type the following:

mental ray for Maya Satellite

raysat2012server.exe /stop raysat2012server.exe /start

mental ray standalone

rayserver.exe /stop rayserver.exe /start

inetd configuration

(Linux with versions of Redhat prior to 7.2) You may need to edit the inetd.conf file located at /usr/etc/inetd.conf and ensure that the following line exists:

mental ray standalone:

mi-ray stream tcp nowait nobody /usr/local/mi35/bin/rayd rayd

mental ray for Maya Satellite

mi-raysat stream tcp nowait nobody /usr/local/mi35/bin/raysatd raysatd

You may need to restart the inetd service by typing the following:

% killall -v -HUP inetd

(Linux only with version of Redhat 7.2 and 7.3) You may need to edit the services in the xinetd.d directory. See To check your xinetd configuration on Linux below.

To check your xinetd configuration on Linux

In a Linux shell type:
```
ls /etc/xinetd.d 
```
There should be a file named mi-ray (mental ray standalone) or mi-raysat (mental ray for Maya Satellite).

If there is no such file, become root, create the mi-ray or mi-raysat file using a text editor and enter the following text:

mental ray:

# description: mental ray for maya network rendering service mi-ray
{ flags = REUSE socket_type = stream user = nobody wait = no server = /usr/local/mi35/bin/rayd log_on_failure += USERID }

mental ray for Maya Satellite:

# description: mental ray for maya network rendering service mi-raysat
{ flags = REUSE socket_type = stream user = nobody wait = no server = /usr/local/mi35/bin/raysatd log_on_failure += USERID }

Save the file.
In order for xinetd to find the newly configured service, you need to restart it or send it a signal.
- Restarting xinetd can be undesirable because it affects a number of network services. To restart xinetd, type:
```
/etc/init.d/xinetd restart
```
- To reconfigure xinetd without restarting it, find out the process id of xinetd by executing:
```
ps -e | grep -v grep | grep xinetd
```
You should see a line similar to this:
```
980 ? 00:00:02 xinetd
```
The first number is the process id of xinetd.

If the system is RedHat 7.2, xinetd re-reads its configuration on receipt of the USR2 signal. For RedHat 7.3 it re-reads its configuration on receipt of the HUP signal. So for a RedHat 7.3 system where xinetd's process id is 980 you would execute:
```
kill -HUP 980
```
xinetd should have found the new service and you should be able to send it render requests from another node on the network.

How do I run multiple versions of mental ray on one machine?

If you want to run different versions of mental ray standalone in one machine, make sure that each version has its own mi-ray* entry in the services file.

For example, if you have mental ray 3.3 and mental ray 3.4 in one machine, and you can change the mi-ray entry for mental ray 3.3 (or 3.4).

Create your own mi-ray variable for mental ray 3.3 in the services file.

The services file might look like this

mi-ray 7003/tcp # used for mental ray 3.4
mi-raysat 7103/tcp # used for mental ray satellite 3.4
mi-ray_33 7155/tcp # used for mental ray 3.3

The server also needs to be updated.

To rename the server file (Windows)

Go to mental ray 3.3 bin directory.
Stop the service (rayserver.exe /stop).
Rename rayserver.exe to ray_33server.exe.
Restart the server (ray_33server.exe /start)

To rename the server file (Linux)

Stop xinet.
Rename rayd to ray_33d.

Create a new file called mi-ray33 in the xinetd.d directory. This file must contain setup information. For example:

{ flags = REUSE socket_type = stream user = nobody wait = no server = /usr/local/mi33/bin/ray_33d log_on_failure += USERID }

Restart the service.

Compatibility issues

Due to a number of changes between mental ray satellite for previous versions of Maya and the current mental ray satellite, there are incompatibilities with using a master (with the current release of Maya) with slaves using a previous version of Maya.

Workaround

Use master and slave machines with the same version of Maya (for example, Maya 8.5 or Maya 8.0).