The
most common reasons, in a Linux or Windows system, that a render
node appears unavailable are that the workstation is offline, the Backburner Server
is not running or is hung, the Server is not using the correct IP
address for the Manager, or the Manager cannot communicate with
the Server.
To resolve an unavailable render node
problem:
- Verify that the render node workstation
is online.
If you are not at the
render node, use the ping command to see this workstation
is online. For help with the ping command,
see
Verifying Communication Between Two Hosts.
If the workstation is
not online, restart the render node, and then see if it appears
in the Backburner network.
If this does not resolve
the problem, continue to the next step.
- Check if the render node is scheduled
to be offline using the Windows-based Backburner Monitor. See
Setting Render Node Availability.
If the render node is
scheduled to be offline and it should be online at this time, change
the schedule for the render node.
If this does not resolve
the problem, continue to the next step.
- Verify the Backburner Server is running.
If it is not running
or is hung, start the Server. Refer to the Autodesk Backburner Installation
Guide for help starting Backburner Server.
NoteIf you are running Backburner Server
as a Windows Service, display the Services control panel, and verify
that the Server service is running. If the service is not running,
highlight it and click Start.
If this does not fix
the problem, continue to the next step.
- For Windows systems only, verify that
the render node can communicate with the correct Manager.
Connect the render node
directly to the Backburner Manager workstation by doing the following:
- Disable any Backburner Server settings
or preferences that automatically connect to the Backburner Manager.
In the Backburner Server General Properties dialog, disable Automatic
Search and manually enter the name or IP address of the Backburner Manager.
- If the render node has more than one
network card, in the Backburner Server General Properties dialog,
manually enter the name or IP address you want to assign to the Backburner Server
in the Server Name or IP Address field.
- Verify that the HOSTS file located in the winnt\system32\drivers\etc\ directory includes
the IP address and corresponding machine name for each render node
and the Backburner Manager workstation on the network. This file
maps machine names to IP addresses.
If restarting the Server
after this step does not fix the problem, continue to the next step.
- If a firewall is running on Backburner network
components, review the firewall settings for each network component
to ensure the following:
- The Backburner application(s) are allowed
to access the network.
- The ports used by the Backburner Manager
and the Backburner Monitor to communicate are not blocked by the firewall.
By default, these ports are 3233 and 3234.
- Verify that the Manager can ping the
render node. See
Verifying Communication Between Two Hosts.
If the Manager can successfully ping the
render node, continue to the next step.
- Configure the log files to report detailed
information about TCP/IP packets, as follows.
Enable the Log Debug
and Log Debug Extended options in the preferences for the Backburner Manager
and the Backburner Server workstations, and then restart the Backburner Manager
and Backburner Server applications.
Examine the TCP/IP information
in the log files to determine why the render node and Backburner Manager
are not communicating.