Open topic with navigation

Setting Up the Render Node Daemon

To set up the daemon, run the batch script _install_daemon.bat on the Render Node computer. During the setup, OctaneRender® asks you to choose a port for Primary Node requests. After that, the daemon resides on that machine, active at all times.

When a Primary Node invokes a daemon, the Render Node launches to get some information about the number of GPUs, version, bitness, etc., and closes again. After that there is no Render Node process running, so the daemon waits for Primary Nodes to detect it by scanning the complete local network in regular intervals. The daemon should appear in the daemon list of the network preferences of the Primary Nodes. If it does not, it could be because:

• The network rendering in the Primary Node is not enabled.
• The daemon is listening on a different port than the Primary Node is scanning.
• The daemon is in a different subnet than the Primary Node is scanning. If you have one ethernet adapter on the daemon and Primary Node PCs, you can ignore this case.
• The Windows^® firewall keeps the Primary Node from connecting to the daemon, or the daemon from responding to the Primary Node. To verify it, disable the firewall on both PCs. If the daemon is now detected (this can take up to 20 seconds), you can try enabling one firewall after the other to see which one is causing trouble.

When you enable a daemon in the Primary Node's settings, the Render Node launches and appears in the Primary Node's status bar. One Primary Node can activate one daemon at a time. If daemon is occupied by another Primary Node, you will see the daemon state change accordingly. The automatic port configuration is an option on the Primary Node that enables the same computer to use multiple Primary Nodes.

The Network Render Node needs to be installed in order to run the Daemon program. It can be downloaded from the Downloads section on the OTOY website (figure 1).

Figure 1: Downloading the Octane Network RenderingThe utilization of multiple CPUs or GPUs over a network to complete the rendering process. Node

Daemons

Daemons are programs that launch after logging in, and it runs all the time unless you shut it down. It fulfills various roles:

• Primary node can locate it in the local network.
• It determines the Render Node's version number and GPUThe GPU is responsible for displaying graphical elements on a computer display. The GPU plays a key role in the Octane rendering process as the CUDA cores are utilized during the rendering process. configuration.
• It starts/stops a Render Node on request by a Primary Node and makes sure that only one Primary Node at a time uses the Render Node.
• It monitors the health of a running Render Node process and kills it if necessary.

To set up the daemon, run Install Octane 2022 Daemon on the Render Node computer (figure 2).

Figure 2: Installing the daemon

Octane asks a series of command line prompts during the installation process. If you want to keep the default settings in the brackets, press Enter (figure 3).

Figure 3: Installing the Octane Daemon

After installing the Octane Daemon, the Render Node Daemon can be run from the Startup folder (figure 4). It launches the next time you log into your Windows® account. A new terminal window appears in your task bar. When you open it, you can see the daemon starting up. At first it tries to launch the render process to gather some information, then it displays that information (figure 5).

Figure 4: Launching the Render Node Daemon

Figure 5: The Octane Network Render Node Daemon command line information

Daemon Installation for MacOS^®

On macOS, the concepts are the same as on Windows. Open the Standalone.dmg file and double-click Install Daemon (figure 6).

Figure 6: Install Daemon command

When the terminal window pops up, enter the daemon port and the IDs of the GPUs you are using for rendering (figure 7). You can also confirm the default values by pressing the Enter key.

Figure 7: Terminal window

After confirming the settings, enter your administrator password. Octane copies the daemon and render node to the Applications folder and sets up a launch agent, which launches the daemon automatically the next time you log in.

Figure 8: Finished installation from the terminal

To run the daemon without logging out and logging in, go into the Applications folder and click on the OctaneRender Daemon application.

Figure 9: Launching the Octane Daemon application

This creates a minimized terminal window in the dock. Select the window from the dock to bring the window up on your desktop.

Figure 10: The daemon terminal

Open topic with navigation