ManagedProcess.HandleStdoutLine: parsing stdout: Error running authentication: No License Model defined [license_impl.cpp(145)]

HI ,

I have a deadline set up in the AWS cloud. set up using AWS Renderfarm python CDK. After successful deployment when I submitted a job, I am getting the following error. I already configured my UBL for deadline

2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout: Error running authentication: No License Model defined [license_impl.cpp(145)]
2023-08-10 07:38:28:  0: STDOUT: Error running authentication: No License Model defined [license_impl.cpp(145)]
2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout: ----
2023-08-10 07:38:28:  0: STDOUT: ----
2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout: Enter the license method:
2023-08-10 07:38:28:  0: STDOUT: Enter the license method:
2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout:   1) Maxon App
2023-08-10 07:38:28:  0: STDOUT:   1) Maxon App
2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout:   2) Maxon Account
2023-08-10 07:38:28:  0: STDOUT:   2) Maxon Account
2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout:   3) Maxon License Server
2023-08-10 07:38:28:  0: STDOUT:   3) Maxon License Server
2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout:   4) RLM
2023-08-10 07:38:28:  0: STDOUT:   4) RLM
2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout:   Q) Quit
2023-08-10 07:38:28:  0: STDOUT:   Q) Quit
2023-08-10 07:38:28:  0: DEBUG: ManagedProcess.Execute: m_process.IsRunning(): True    m_process.IsStdoutAvailable(): False
2023-08-10 07:38:28:  0: DEBUG: PopupHandler.CheckForPopups: Getting popup handles
2023-08-10 07:38:28:  0: DEBUG: PopupHandler.CheckForPopups: Got 0 handles
2023-08-10 07:38:28:  0: DEBUG: PopupHandler.CheckForPopups: Returning
[ ... last message continued until job got canceled ... ]```

Hello

Thanks for reaching out. Seem like it is Cinema 4D UBL? I would be curious to know how did you make this AMI you are using to render or are you using one of our Cinema 4D AMIs?

I would check the verbose License Forwarder logs and Worker logs.

  • Please enable verbose logging: To enable verbose logging of Deadline application configure it from Deadline Monitor> Tools> Configure Repo Options> Application Data (left pane)> check option for verbose logging (bottom right pane)> restart the
  • Restart the License Forwarder (LF) from Deadline Monitor> View> New Panel> License Forwarder> Right Click> Remote Control LF> LF Commands> Restart LF>
  • Restart the Worker> From Deadline Monitor’s Workers Panel> Right click the Worker> Remote Control> Worker Commands> Restart Worker
  • Reproduce the issue and share the License Forwarder logs and Worker logs, ideally from the application logs directory stored locally on the machine running these nodes. If you cannot access them then you can share the streamed logs: from right menu of LF and Worker.
  • Did you apply Cinema4D UBL limit to the job in question?

For UsageBasedLicensing/Cluster/ASG I used amzn2-ami-ecs-hvm-2.0.20230731-x86_64-ebs
For RenderQueue/Cluster/RCS Capacity → amzn2-ami-ecs-hvm-2.0.20230731-x86_64-ebs
and
for Worker Deadline Worker Base Image Windows 10.2.1.1 with Cinema4D 26.107 and V-Ray 5.20.06 and Arnold 4.3.0 2023-04-18T012356Z then created own ami installing NVIDIA drivers in it