AWS Thinkbox Discussion Forums

Could not initialize the plugin sandbox

Hello,

I’m running Deadline 10.1.16.9 with houdini 18.0.499.
I try to launch PDG tasks on my local farm and I got this error:

Error

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

Failed to load the plugin because: Could not initialize the plugin sandbox (Deadline.Plugins.PluginException)

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

Type

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

RenderPluginException

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

Stack Trace

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

at Deadline.Slaves.SlaveRenderThread.e(String aix, Job aiy, CancellationToken aiz)

at Deadline.Slaves.SlaveRenderThread.b(TaskLogWriter ait, CancellationToken aiu)

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

Log

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

2021-06-23 15:32:13: 0: Loading Job’s Plugin timeout is Disabled

With the same setup it was working before I updated Deadline to the latest version (I can’t remember which version it was)

I tried reinstalling the repository and the deadline client , same issue
I reinstalled Houdini , still same issue.
Deadline works with ROPs and renders , I only have this issue with PDG

Don’t really know what is the problem.

Can someone help me ?

This can happen if you have a PYTHONPATH specified in the Job Environment which is a different version of python to say what Deadline is configured to use.

Did you add $HFS to the config options?
https://www.sidefx.com/docs/houdini/nodes/top/deadlinescheduler.html

wrong thread…
sorry… adding extra words to meet minium post lenght

Did anyone get this to work. I am having the same issue with PDG. It worked on deadline before we upgraded and now the same PDG template I was running is giving the the error: Failed to load the plugin because: Could not initialize the plugin sandbox (Deadline.Plugins.PluginException)

Did you get this to work?

Nope. We are on deadline 10.1.15.2 and I was told that its been fixed in 10.1.18. But I need to wait for my company to upgrade. I could not come up with a work around, I was just going to test in a staging area on an upgraded version to confirm.

Privacy | Site terms | Cookie preferences