AWS Thinkbox Discussion Forums

Completed Jobs Not Completing

Hello,

We’re having an issue where Deadline will finish rendering a job, but won’t move on to the next without being manually set to “Complete”. We’re running 10.3 along with C4D 2024 and Redshift. We’ve tried reaching out to Maxon support regarding the Maxon App possibly causing issues but haven’t come to any resolution. It doesn’t seem like that is the source of the problem. As you can see from the log below, everything concludes normally. Deadline just doesn’t go to pick up a new job and shows as “Rendering” indefinitely. Appreciate any help!

2024-07-19 12:51:31: 0: STDOUT: Redshift Debug: Freeing GPU mem…(device 0)
2024-07-19 12:51:31: 0: STDOUT: Redshift Debug: Done (CUDA reported free mem before: 4275 MB, after: 43373 MB)
2024-07-19 12:52:35: 0: STDOUT: Redshift Debug: Summary: Profile: Update:00:02.258 (00:02.164/00:00.000/00:00.094/00:00.000) Render:10:20.284 (00:11.759/00:05.526) Output:01:08.565 Total:11:31.108
2024-07-19 12:53:28: 0: STDOUT: Redshift Debug: Context: Unlocked:Render
2024-07-19 12:53:28: 0: STDOUT: Progress: 100%
2024-07-19 12:53:28: 0: STDOUT: Rendering successful: 901.203 sec.
2024-07-19 12:53:28: 0: STDOUT: Warning: Unknown arguments: true
2024-07-19 12:53:28: 0: STDOUT: Redshift Debug: PreviewScheduler: Flush/Clear Context
2024-07-19 12:53:28: 0: STDOUT: Redshift Debug: PreviewScheduler: End
2024-07-19 12:53:28: 0: STDOUT: Redshift Debug: PreviewScheduler: Flush completed
2024-07-19 12:53:29: 0: STDOUT: Redshift Debug: Shutdown mem management thread…
2024-07-19 12:53:29: 0: STDOUT: Redshift Debug: Shut down ok
2024-07-19 12:53:29: 0: STDOUT: Redshift Debug: PostFX: Shut down
2024-07-19 12:53:29: 0: STDOUT: Redshift Debug: Shutdown GPU Devices…
2024-07-19 12:53:29: 0: STDOUT: Redshift Debug: Devices shut down ok
2024-07-19 12:53:29: 0: STDOUT: Redshift Debug: Shutdown Rendering Sub-Systems…
2024-07-19 12:53:29: 0: STDOUT: Redshift Info: License returned
2024-07-19 12:53:29: 0: STDOUT: Redshift Debug: Finished Shutting down Rendering Sub-Systems
2024-07-19 12:53:29: 0: STDOUT: MaxonEnd: 07/19/24 at 12:53:29

I am having the same issue

except I am on Octane

a chunk of frames will complete rendering, but then not move on to the next task

It also seems that … C4D is closing before it can be told to close by deadline? if that is the issue??

Interesting that it is on Octane. I’m not sure what licensing you’re using but could you try opening the Maxon App the next time this happens? It’s sometimes frozen/looping for me. Curious if it does for you

Which licensing is doing that for you?
I switched my Thinkbox Deadline nodes to ‘no license’ (now that they require no license for under 10 nodes)

I do have a pack of 5 C4D command line render licenses – and in my config.commandline.txt file I have it set to login using credentials VS the app

g_licenseUsername=“xxx”
g_licensePassword=xxx

if this is what you mean?

I feel like the Maxon app is always fighting the licensing no matter what

I can’t seem to determine what is causing this from the error logs

ExceptionNumber = 0xC0000005
ExceptionText = ACCESS_VIOLATION
Address = 0x00007FFDB2714E2E
Thread = 0x0000000000004AF0
Last_Error = 0x00000000

I still need to submit a nearly-empty scene and render with standard renderer to help determine exactly where the error is

We have less than 10 nodes so we are also not using Thinkbox license. I didn’t purchase the C4D license but it’s designated as Cinema + Redshift (Teams) in the online assignment.

I recently did install the GUI-less Maxon One shown below but I haven’t edited my config with user and password.

Could you share where you’re getting these error logs? And did this issue come up after a certain update/release for you?

That error was in a bugreport - (I don’t remember if it was C4D or Octane bug report)
But – under the appdata/roaming/maxon/c4d2024/bugreports

I submitted a scene without octane (just using standard renderer), and it went through just fine on all of the computers…

Not saying it’s necessarily Octane, could be a conflict with the GPU driver… (in my case)

I’ll report back if I figure anything out.

I forget exactly when it was that I started having issues…
My problem stemmed from a Maxon update near the beginning of the year that required me to do a big leap in versions with Octane. – well, then that required a gpu driver update, and octane wasn’t happy with that driver version… which led me into a Ménage à trois of a deathspiral of never-ending 3 points of failure that don’t work together.

Not to mention the maxon app integration with licensing has been a disaster for the last few years. It trips over itself trying to re-license and un-license in between each grouping of frames submitted, which causes problems with license cooldown times.

Gotcha. This sounds a lot like the rabbit hole I went down. Maxon App appears to refresh connection each time license is grabbed and released when between and after tasks. Occasionally I’d see the Deadline log report the Maxon App can’t be reached and need to be restarted or something.

Hi @Jesse_Stormer, Have you found a resolution for this problem? It’s still going on for my nodes. I’ve recently added a new rendering machine and it seemed to work fine for a few weeks until recently again.

Privacy | Site terms | Cookie preferences