Error when running jobs on Ubuntu 22.04LTS

Deadline
1

Hello, I am running 10.3.0.9 with nodes on Ubuntu 22.04 LTS and I have this error when rendering on the farm:

Error

=======================================================

The Deadline Plugin was not properly initialized. Application plugins must explicitly call super().__init__() in the Python constructor: def __init__().

Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgt, CancellationToken bgu)
at Deadline.Plugins.SandboxedPlugin.Initialize(Job job, CancellationToken cancellationToken)
at Deadline.Slaves.SlaveRenderThread.e(String aka, Job akb, CancellationToken akc)
at Deadline.Slaves.SlaveRenderThread.b(TaskLogWriter ajw, CancellationToken ajx)

=======================================================
Log

2023-08-12 21:21:13: 0: Loading Job’s Plugin timeout is Disabled
2023-08-12 21:21:13: 0: SandboxedPlugin: Render Job As User disabled, running as current user ‘tang’
2023-08-12 21:21:15: 0: Executing plugin command of type ‘Initialize Plugin’
2023-08-12 21:21:15: 0: INFO: Executing plugin script ‘/var/lib/Thinkbox/Deadline10/workers/render-1/plugins/64d859e83b6abfbe42800aef/Houdini.py’
2023-08-12 21:21:16: 0: INFO: Plugin execution sandbox using Python version 3
2023-08-12 21:21:16: 0: Encountered an error while executing plugin command of type ‘Initialize Plugin’
2023-08-12 21:21:16: 0: Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.
2023-08-12 21:21:16: 0: at Deadline.Plugins.DeadlinePlugin.CancelTask()
2023-08-12 21:21:16: 0: at Deadline.Plugins.PluginWrapper.CancelTask()
2023-08-12 21:21:16: 0: at Deadline.Slaves.CommandListener.e(String air)
2023-08-12 21:21:16: 0: at Deadline.Slaves.CommandListener.d(Object aiq)
2023-08-12 21:21:16: 0: at Deadline.Slaves.CommandListener.b(DeadlineMessage aio, Exception aip)
2023-08-12 21:21:16: 0: at Deadline.Net.DeadlineMessageUtils.a.a(IAsyncResult bhs)
2023-08-12 21:21:16: 0: at System.Threading.Tasks.TaskToApm.TaskAsyncResult.InvokeCallback()
2023-08-12 21:21:16: 0: at System.Threading.Tasks.AwaitTaskContinuation.<>c.<.cctor>b__17_0(Object state)
2023-08-12 21:21:16: 0: at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
2023-08-12 21:21:16: 0: — End of stack trace from previous location —
2023-08-12 21:21:16: 0: at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
2023-08-12 21:21:16: 0: at System.Threading.Tasks.AwaitTaskContinuation.RunCallback(ContextCallback callback, Object state, Task& currentTask)
2023-08-12 21:21:16: 0: — End of stack trace from previous location —
2023-08-12 21:21:16: 0: at System.Threading.Tasks.Task.<>c.b__128_1(Object state)
2023-08-12 21:21:16: 0: at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute()
2023-08-12 21:21:16: 0: at System.Threading.ThreadPoolWorkQueue.Dispatch()
2023-08-12 21:21:16: 0: at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
2023-08-12 21:21:16: 0: at System.Threading.Thread.StartCallback()

Any Idea ?

I tried Maya and Houdini same results.

Thank you

Tanguy

2

The error is right there at the top. The constructor must call its superclass’s constructor.
Do you perhaps have your own overrides of plugins? Or old plugins in the custom directory?
I can see in our version (10.2) of Deadline that the super constructor is not being called.

3

It seems like a version mismatch between the Worker and the Repository plugin. It seems like the Deadline Client is running 10.3 version and the python plugin its pulling is older. You would need to upgrade Deadline Repository to the same version as of the render node.

If you are using a custom plugin based of Python version less than 3.10, you can follow this knowledge base article to fix it.

1 Like
4

Hello thank you for the reply, I am running 10.3.0.9 on the repo side, but I installed without removing the previous one. Maybe that is the issue.
I will give it a try today and do a fresh install on the repo side