|
|
||
    |
||
- EnFuzion for Render Farms fails to connect to the Control Root
- My jobs complete successfully, but 'Show Image' does not show any images
- My rendering fails to complete successfully
- My output images are not correct
- 3ds Max: Using 3ds Max 8 on Compute Nodes
- After Effects: After Effects fails to render on Mac OS X platform
- CINEMA 4D: CINEMA 4D fails to render
- Maya: Maya fails to render on Mac OS X platform
- Maya: Some Maya frames fail to render on Mac OS X platform
- Maya: The Thumbnail Browser does not show tiles
- Maya: Maya frames fail to render on heterogeneous render farms
- Alias mental ray: How do I generate .mi files from a command line or with a script
- Alias mentay ray: How do I configure compute nodes for Alias mental ray Standalone
- XSI: Image viewer Flip.exe fails on Windows
- XSI: Image converter imgconv.exe fails on Windows
- Windows 7 and Windows Server 2008 Setup
- I am unable to connect to the EnFuzion Web
- How do I verify that the EnFuzion Root is running
- The enfdispatcher process is not running on the EnFuzion Root computer
- How do I configure EnFuzion Root Computer to start EnFuzion at the boot time
- How do I configure EnFuzion Root Computer to start EnFuzion at the boot time on Windows
- How do I configure EnFuzion Root Computer to start EnFuzion at the boot time on Mac OS X
- How do I configure EnFuzion Root Computer to start EnFuzion at the boot time on Linux
- How do I install an EnFuzion license key
- How do I verify that the EnFuzion Node in my cluster is working
- How do I verify that the EnFuzion Node is running on the host
- The enfnodeserver process is not running on the EnFuzion Node computer
- The enfnodeserver process is not running on the EnFuzion Node computer on Windows
- The enfnodeserver process is not running on the EnFuzion Node computer on Mac OS X
- The enfnodeserver process is not running on the EnFuzion Node computer on Linux
- An EnFuzion Node is not connecting to the EnFuzion Root
-----------------------------------------------------------------------------------------------------------------------------------
TROUBLESHOOTING IMAGE RENDERING
Select Tools:Test Control Root Access.
This opens a dialog for testing the connection. Press Test Connection button.
If the test is successful, then EnFuzion for Render Farms is connected.
If the test fails, then verify the address of the EnFuzion Control Root in the file
If the address is correct, then verify that the EnFuzion Control Root is operational and accessible over the network.
The EnFuzion Image Browser uses the Maya fcheck or the XSI flip utility to display images. You must have Maya or XSI installed for this feature to work properly. Fcheck is tried first, flip is tried second. If you wish to use a different viewer, please contact Axceleon at support@axceleon.com
Select the run with failed jobs and double click on the run to open its Job List window. Check the Show All checkbox in the upper right corner. This will show all job retries, including rescheduled jobs. Select a job which causes problems and right click or Ctrl click on Mac OS X to display the job menu.
Select Show Render Log to view the render log produced by the renderer. Check out the log for any error messages or notices from the renderer that might help to diagnose the problem.
If the render log does not exist or if the log does not contain any indication of the problem, select Show Render Standard Output to view the standard output and Show Render Standard Error to view the standard error. These entries show any messages that are recorded to the standard output and the standard error files by the renderer and other programs.
If Show Render Standard Output and Show Render Standard Error do not help, select Show Render Command. This entry displays the command that EnFuzion used on a Compute Node to render the image. Verify that the command is correct by logging into the Compute Node and typing the command in the Command Prompt. If the command fails, then there is a problem with the rendering application, access to the project files or environment variables on the node. Additional entries in the menu help with the problem identification.
Select Show EnFuzion Job Log to view any additional messages from EnFuzion. This log contains all major events during the job execution as well as all EnFuzion errors for the job. Most common problems that are identified in the log are:
- the file or a directory is not found:
The node is unable to access project files. Verify that the project files are shared over the network and accessible to compute nodes. - the following user command exited with status code:
The rendering application failed to complete successfully. Verify that the rendering application is installed on the node, verify the environment variables required by the application and check out the render log, the standard output and the standard error for any error messages.
If the problem persists, select Zip Diagnostic Files. This produces the zip file run-
Make sure that your scene and your render global parameters are correct by rendering several images locally on your workstation before submitting the scene to your render farm.
If images are correctly rendered locally, but fail to render on the render farm, check out the section on failed rendering.
If you use 3ds Max 8 on a Compute Node, make sure that previous versions of 3ds Max on the same machine are uninstalled and their directories deleted.
If no user is logged in on the Mac OS X platform, then rendering might fail with the following message:
INIT_Processeses(), could not establish the default connection to the WindowServer
There are two workarounds to avoid this situation:
- Login the enfuzion user permanently;
- Set the ownership of the After Effects aerender command to root with the following commands:
cd /Applications/Adobe After Effects 6.5
sudo chmod +s aerender
sudo chown root aerender
Verify that your scene is prepared for rendering on an EnFuzion render farm. The logging in the scene must be turned on. To turn on the logging, open the scene in CINEMA 4D and select Render Settings:Options, turn on Log File.
If the logging is turned on, but the scene is still not rendering, then verify that your Compute Node is configured for rendering with CINEMA 4D. The enfuzion user on the node must have write, read and modify permissions to the CINEMA 4D directory, so that it can manage the render log. These permissions are turned on as follows:
- right click on C:\Program Files\MAXON\CINEMA 4D R9 in Explorer;
- select Properties:Security;
- under Group or user names:, select Users;
- under Permissions for Users:, turn on Full Control;
- click OK.
If no user is logged in on the Mac OS X platform, then rendering might fail with the following message:
INIT_Processeses(), could not establish the default connection to the WindowServer
There are two workarounds to avoid this situation:
- Login the enfuzion user permanently;
- Set the ownership of the Maya Render command to root with the following commands:
cd /Applications/Alias/maya7.0/Maya.app/Contents/bin
sudo chmod +s Render
sudo chown root Render
The rendering sometimes fails with a message similar to the one below:
2005-08-14 21:33:45.693 MayaBatch[2781] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2e03, name = 'Processes-0.7471105' See /usr/include/servers/bootstrap_defs.h for the error codes.
2005-08-14 21:33:45.694 MayaBatch[2781] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (Processes-0.7471105) CFMessagePortCreateLocal failed (name = Processes-0.7471105 error = 0)
The solution is to reboot the machine. There is no need to resubmit your Scene as EnFuzion automatically reschedules the failed jobs to other available machines.
This feature is not yet supported. The View Thumbnail feature does not work for frames rendered in tiles.
Your render farm is heterogeneous if one or more Compute Nodes run a different operating system than your Submit Computer.
All external texture and other file references in the scene must be relative to the Maya project. EnFuzion automatically adjusts path values between different platforms when it calls the renderer from a command line. EnFuzion will not change any paths that are specified in the scene itself. If you want to use file paths that are not relative to the project and have a heterogeneous render farm, please contact Axceleon at info@axceleon.com.
The following command takes a Maya scene and generates .mi files:
maya -batch -command "Mayatomr -mi -pf 2 -file
EnFuzion provides a separate script to configure mental ray Standalone. This script is
When you try to use Softimage flip.exe to view images, the program might fail with the following message:
flip.exe - Unable to Locate DLL
The dynamic link library ilcor10.dll cannot be found ...
In this case, find ilcor10.dll on your system and add the directory it is located in to the PATH environment variable on your system or copy ilcor10.dll to the directory with flip.exe.
When EnFuzion tries to use Softimage imgconv.exe to convert images to thumbnail JPEGs, the program might fail to work.
In this case, make sure that the SI_IMAGE_PATH environment variable is set to
When installing EnFuzion on Windows 7 or Windows Server 2008 please disable UAC.
UAC will inhibit EnFuzion from running. Please see attached Tech Note for more details at http://www.enfuzion3d.com/Tech_Note_E3D-TN102.pdf
TROUBLESHOOTING ENFUZION CONTROL ROOT
Verify that the URL address in your Web browser is correct. The EnFuzion Web address is:
http://
You should be greeted by the EnFuzion Welcome page.
If the EnFuzion Welcome page is not displayed, verify that EnFuzion Root is running and that the network to the EnFuzion Root host is working.
If the EnFuzion Welcome page is displayed, click on the Cluster link in the header to verify EnFuzion operation.
If the Cluster link returns a General Error page, then verify that the EnFuzion Root is running.
On Windows, open Task Manager and confirm that the following processes are running: enfDispatcher.exe and enfeye.exe.
On Mac OS X and Linux, execute the following command line:
ps ax | grep enf
Confirm that the following processes are running: enfdispatcher and enfeye.bin.
If the enfeye process is not running, reboot the machine.
If the enfdispatcher process is not running, check out the enfdispatcher section.
Verify in the Task Manager on Windows or with the ps ax command on Mac OS X and Linux that there is no enfdispatcher process.
If there is no enfdispatcher process, check out the dispatcher log for any error messages. The dispatcher log is located in the directory
If the EnFuzion license key is missing or invalid, install the key.
If your working disk is running out of space with less than a few Mb available, EnFuzion Root software records this in the log and preventively terminates. Delete redundant files and reboot the machine or restart EnFuzion.
If the log file
If there is still no enfdispatcher process and no enfuzion.log file after the machine is rebooted, verify that EnFuzion is configured to start at the boot time.
Check out sections for specific computing platforms: Windows, Mac OS X and Linux.
On Windows, the default option of the EnFuzion graphical installer is to automatically configure the computer to start EnFuzion at the boot time. To configure the computer manually, select the menu item Start:All Programs:EnFuzion:Control Root Utilities:Register EnFuzion Root service. To start EnFuzion, select the menu item: Start:All Programs:EnFuzion:Control Root Utilities:Start EnFuzion Root service.
If the EnFuzion does not start after the reboot, verify all the steps in the section about the enfdispatcher process not running.
If the EnFuzion still does not start and there is no log in
Verify that the EnFuzion startup files are installed. The files are in the directory /Library/StartupItems/EnFuzion. The directory should include two files, EnFuzion and StartupParameters.plist.
If the directory or the files do not exist, go to the directory with an unpacked EnFuzion distribution and execute:
sudo ./install-service
If the directory and the files exist, verify that EnFuzion is listed in the system startup file. The system startup file is /etc/hostconfig. The file should contain a line:
ENFUZION=-YES-
To start EnFuzion, execute the following command line:
sudo SystemStarter start "EnFuzion Control Root Service"
Verify that the EnFuzion startup script is installed. The script is in the file /etc/init.d/enfuzion.
If the file /etc/init.d/enfuzion does not exist, go to the directory with an unpacked EnFuzion distribution, log in as a root user and execute:
./install-service
If the file /etc/init.d/enfuzion exists, verify that EnFuzion is on the list of services that are started at the boot time. Execute the command:
chkconfig --list | grep enfuzion
Output should include several on levels:
enfuzion 0:off 1:off 2:on 3:on 4:on 5:on 6:off
To start EnFuzion, execute the following command line:
/etc/init.d/enfuzion start
EnFuzion license keys are stored in file
If the license key file does not exist, copy your EnFuzion license key to
If the license key file exists, but the enfdispatcher process is not running, verify that there are no messages about an invalid license in the EnFuzion log file in
If your license key is invalid then the log file contains messages similar to the following:
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 create port 10102
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 message build 9.0.006 for Linux 2.4.5-3smp i686
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 message reading root options from file "/home/john/enfuzion/config/root.options"
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 message the license file "/home/john/enfuzion/config/enflicense.txt" contains an invalid EnFuzion Root license.
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 message The license is invalid for the following reasons:
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 line 2: day date 16 1 2006, expired 15 12 2005
Verify that the content of
If your EnFuzion license key expired, send a request for a new license key to support@axceleon.com.
For an additional assistance, report the problem to support@axceleon.com and include
TROUBLESHOOTING ENFUZION COMPUTE NODE
Open the EnFuzion Web page in your Internet browser:
http://:10101
Click on the Nodes link in the header to obtain the Nodes table.
Under the Host column, find the host name for the Node and check its Status.
If the node status is Idle, Executing or Busy, then the Node is working.
If the host name is not in the table or if its status is Down, then the Node is not working. In that case, verify that the EnFuzion Node is running on the host.
On Windows, open Task Manager and confirm that the following processes are running: enfStarterSvc.exe and enfNodeServer.exe.
On Mac OS X and Linux, execute the following command line:
ps ax | grep enf
Confirm that the following process is running: enfnodeserver.
If the enfnodeserver process is not running, check out the enfnodeserver process section.
If the enfnodeserver process is running, confirm that the node is not working, using the EnFuzion Web.
If the enfnodeserver process is running, but the node is not working, then the Node is not connecting to the EnFuzion Root. Check out the section on Node is not connecting.
Check out sections for specific computing platforms: Windows, Mac OS X and Linux.
Verify in the Task Manager that there is no enfnodeserver process.Check out the Starter Service log for any messages. The log is located in the file
A common problem is an invalid user name or password. The Starter Service log contains the following line:
Thu Jan 12 20:00:41 2006: Logon failed for user 'enfuzion' - Logon failure: unknown user name or bad password.
In this case, create the user on the local machine or provide a correct password. If the Node is defined locally, then the password is stored in the file
If you change the service.config.txt file, then you must restart the Node. Stop the Node by selecting the menu item Start:All Programs:EnFuzion:Compute Node Utilities:Stop EnFuzion Node service. Start the Node by selecting the menu item Start:All Programs:EnFuzion:Compute Node Utilities:Start EnFuzion Node service.
If you change the enfuzion.nodes.txt file, then you must restart the EnFuzion Root. Stop the Root by selecting the menu item Start:All Programs:EnFuzion:Control Root Utilities:Stop EnFuzion Root service. Stop the Node by selecting the menu item Start:All Programs:EnFuzion:Control Root Utilities:Start EnFuzion Root service.
If the enfnodeserver process is still not running and there are no error messages in the Starter Service log, then check out the Node Server log. The log consists of two files in the directory
If the problem is not evident from the Node Server log, then send a report to support@axceleon.com and include files enfstarter.log, enfnodea.log and enfnodeb.log.
Verify with the ps ax command that there is no enfnodeserver process.
Verify that the EnFuzion Node startup files are installed. The files are in the directory /Library/StartupItems/EnFuzionNode. The directory should include two files, EnFuzionNode and StartupParameters.plist.
If the directory or the files do not exist, go to the directory with an unpacked EnFuzion distribution and execute:
sudo ./install-svcnode
If the directory and the files exist, verify that EnFuzion is listed in the system startup file. The system startup file is /etc/hostconfig. The file should contain a line:
ENFNODE=-YES-
To start EnFuzion, execute the following command line:
sudo SystemStarter start "EnFuzion Compute Node Agent"
If the enfnodeserver process is still not running, then check out the Node Server log. The log consists of two files in the /tmp directory. Files are called .enfnodea.log and .enfnodeb.log. EnFuzion uses a circular double buffering to keep the file sizes limited. The file with the latest entries contains the latest reports. The files contain any critical error messages by the Node.
If the problem is not evident from the Node Server log, then send a report to support@axceleon.com and include files .enfnodea.log and .enfnodeb.log.
Verify with the ps ax command that there is no enfnodeserver process.
Verify that the EnFuzion startup script is installed. The script is in the file /etc/init.d/enfnode.
If the file /etc/init.d/enfnode does not exist, go to the directory with an unpacked EnFuzion distribution, log in as a root user and execute:
./install-svcnode
If the file /etc/init.d/enfnode exists, verify that EnFuzion is on the list of services that are started at the boot time. Execute the command:
chkconfig --list | grep enfnode
Output should include several on levels:
enfnode 0:off 1:off 2:on 3:on 4:on 5:on 6:off
To start EnFuzion, execute the following command line:
/etc/init.d/enfnode start
If the enfnodeserver process is still not running, then check out the Node Server log. The log consists of two files in the /tmp directory. Files are called .enfnodea.log and .enfnodeb.log. EnFuzion uses a circular double buffering to keep the file sizes limited. The file with the latest entries contains the latest reports. The files contain any critical error messages by the Node.
If the problem is not evident from the Node Server log, then send a report to support@axceleon.com and include files .enfnodea.log and .enfnodeb.log.
Verify that there is no active firewall on the EnFuzion Root Computer. If a firewall is required on the EnFuzion Root Computer, then configure EnFuzion to use static port numbers. Perform the following steps on the EnFuzion Root Computer:
add the following line to
jobport 10104
in the firewall configuration, open the following ports:
10101, 10102, 10103, 10104;
restart EnFuzion on the Root Computer.
Verify in the Task Manager on Windows or with the ps ax command on Mac OS X and Linux that the enfnodeserver process is running.
If the process is not running, check out the section on Node is not running.
If the enfnodeserver process is still not running, then check out the Node Server log. The log consists of two files. On Windows, files are called enfnodea.log and enfnodeb.log and are in the
If the problem is not evident from the Node Server log, then send a report to support@axceleon.com and include the files enfnodea.log and enfnodeb.log.
Copyright 2010 © Intellectual Property Axceleon Inc.