Octane Network Crashes Tweet

[Powel2097]

Hi there,

I am experiencing crashes of cinema everytime Netwrok rendering is enabled.
The scene renders fine without it.
When enabled, it crashes, sometimes in the beginning, sometimes after 10 frames, or even more.

It is happening in every scene. even in a simple one with only a cube spinning.

Sometimes the Slave console shows CUDA Error 700. But not always.
Or the rendering freezes at one frame until I disable the network render option, and then it keeps rendering only on the Master.

Out of core beeing enabled or disabled doesnt help.
Octane doesnt save a Log.
But Cinema does, see attached.

Both are running latest stable versions 2020.1.5
Both have the latest Studio Drivers instaleld.

Master:
Windows 10 Pro
Ryzen 9 3950X
128GB Ram
4x 2080ti

Slave:
i7-6800K
16 GB Ram
1x 2080
2x 2070 Super

Any ideas?

[bepeg4d]

Hi,
please, open the scene, then go to c4doctane Settings/Other tab, and, at the bottom of the panel, enable all the Log option checkboxes:

Then, load the scene in Live View with Net render active, then in Picture Viewer, until crash, and share the c4doctanelog.txt file that you find in c4doctane directory, or in the path specified in Settings/Other panel, thanks.

ciao Beppe

[Powel2097]

Here it is,
crashed after 4 frames.
no errors on the slave console.

[bepeg4d]

Sorry, please, open the scene, then go to c4doctane Settings/Other tab, and, at the bottom of the panel, enable all the Log option checkboxes.
Then, load the scene in Live View, then in Picture Viewer, or until crash, then reopen c4d, navigate to c4doctane Settings/Other tab, press the Generate log report button, and share the octanelog_report.zip file, thanks.


ciao Beppe

[Powel2097]

here we go:

[bepeg4d]

Ok, thanks.
I think that the issue is in the Render-Node.

It is possible to generate a log from the daemon, and run it in a more verbose mode.

Please, copy paste the attached octane_daemon_log.txt file in the Render-Node directory:

octane_daemon_log_flags.txt.zip

(911 Bytes) Downloaded 124 times

Then please perform the same Network rendering session.
Then navigate to `C:\Users\UserName\AppData\Local|temp`, or write %TEMP% in the Explore path field.
Locate the octane_damon_log.txt file and share it to me, thanks.

Please, also download and run GPU-Z:
https://www.techpowerup.com/gpuz/
And share a screenshot from the Graphics Card tab, for all the available Nvidia GPUs in the Render-Node machine, thanks:


ciao Beppe

[Powel2097]

Alright,

so during the render, it rendered 4 frames á 30 sec and then rendered one frame for more than 4 minutes without change.
So I disabled network rendering and enabled again.
then it rendered a coupe of frames and stopped completly using the slave and rendered by it´s own.
The slave crashed completly. Usually, when the slave crashes, nothing happens on the slave, just cinema on the Master crashes.

Second render took a while to crash.

It didnt create the log file. just a file called "octane" in the temp folder.
In the console, I saw the new messeges heartbeat, etc---


Not sure if this is relevant, but the Slave is not connected to a monitor.
No cable on the GPU´s.

And the set up Port on the Master is 1080. also when installing the render Node.
But In the console it says, using free port 1081.

attaches are 2 octane files, a and b. from first and second crash.

[Powel2097]

missed the 2 files.

[Hatsize7]

I had a similar problem today on a slave, which was a new build and I forgot to turn off the sleep mode in Windows. Any chance that it's a new Windows with those settings on? Maybe a Windows update turned them back on?
Also, you indicated that your slave has only 16Gb RAM. How big is your scene? It might be running out of ram?
I'm just guessing here, someone from the Octane team will probably give you a straight answer.

[bepeg4d]

Hi Powel2097,
thanks for sharing the daemon logs.

System RAM should not be an issue, at least with this scene.
Have you updated Win 10 to 2004 in the Render-Node machine?

If yes, try to clean install the same Nvidia 456.38 driver of the Workstation/Master.

ciao Beppe