I’m dealing with a bit of an unusual situation and could use some advice. I have two machines: one with a licensed version of Redshift (RS) and one without. Both machines have Houdini and Redshift installed, allowing me to open scenes without causing issues. Everything works fine in the GUI.
However, when I try to run simulations or any Houdini-related tasks on the unlicensed machine using Deadline to manage the queue, Houdini starts but then just hangs. There’s no error message, and the CPU usage is zero.
If I disable RS from the package, Houdini throws errors about missing RS nodes since RS isn’t installed, but it doesn’t hang. On the other hand, if I send a scene that’s been cleared of RS nodes, everything works perfectly.
Is it possible that Redshift is causing issues by trying to find a license unnecessarily when using Deadline? Are there any known workarounds for this?
I was curious because I remember seeing something similar while testing. I was able to make Houdini crash on the commandline render. As a quick test, I just pointed redshift_LICENSE to something bogus. Houdini 20.5.278 RS 3.6.04
Maxon redshift log reported:(I just remembered that this box above used to have a node-locked license)
17:25:45 3584MB ERROR: Maxon licensing error: User not logged in Domain: General (2)
17:25:45 3584MB ERROR: Writing Redshift crash dump to C:\Users\deadline\AppData\Local\Temp\Redshift\20240819-172545-12404-23468.dmp
and on another box there is a dialog box /window popping up asking about “mxapp”, but the logs show:
17:46:00 3971MB ERROR: Maxon licensing error: Please update your Maxon App to at least version 2024.2 (current version ). (16)
17:46:00 3970MB ERROR: Writing Redshift crash dump to C:\Users\deadline\AppData\Local\Temp\Redshift\20240819-174600-6896-13024.dmp
I removed all but the one active ROP export nodes, (I had around 20). The hang time reduced from 15mn to 3mn. I disabled path mapping as this is the last info I get on the log before it hangs “Begin path mapping.” That didn’t change a thing, and this message is still displayed as if it had not been disabled.