Deadline 7.1 Ignoring Env Variables

Deadline
1

Hi,
We had deadline 7.1 working fine for a while, but we recently had to re-install (new server) and we can’t get it to work. Deadline itself works fine, however all of our env variables are being ignored/overridden.
We have variables set in /etc/profile.d/render.sh
these work, as we can test using kick, it loads our shaders and checks out a license. But when we render the same ass file via deadline, our shaders aren’t loaded and our license isnt checked out. We have restarted the machines to ensure our variables are loaded, checked to make sure the variables are loaded for the render user, and via sudo, and under the root account.

[jedipottsy@thor ~]$ echo $RLM_LICENSE 5053@10.0.0.6 [jedipottsy@thor ~]$ sudo echo $RLM_LICENSE 5053@10.0.0.6 [jedipottsy@thor ~]$ sudo su -c 'echo $RLM_LICENSE' 5053@10.0.0.6 [root@thor jedipottsy]# echo $RLM_LICENSE 5053@10.0.0.6

Again, running kick manually from the command line it works fine, but deadline produces magenta renders with arnold watermarked.

(Were running Centos 7.2 on workstation and render nodes, but cent 6.7 on the license/pulse server (10.0.0.6 is our license and deadline/pulse server)).

2

The big thing that can influence environment variables is the “run as user” option. Some info on where that feature is over here:
docs.thinkboxsoftware.com/produc … r-security

There’s a quick write-up here on environment with sudo which you’ve likely already taken into account:
docs.thinkboxsoftware.com/produc … -with-sudo

For testing the environment, I usually submit a job which runs /bin/sh with “-c set” as arguments. That will at least give some visibility while you’re working on this…

Are you using “run as user” by any chance?

3

I thought that might be it, it is started as user (jedipottsy) to avoid nfs permission issues.

i did add this to visudo

Defaults        env_keep += "MAYA_DISABLE_CIP"
Defaults        env_keep += "MAYA_DISABLE_CER"
Defaults        env_keep += "MTOA"
Defaults        env_keep += "MAYA_PLUG_IN_PATH"
Defaults        env_keep += "MAYA_MODULE_PATH"
Defaults        env_keep += "MAYA_RENDER_DESC_PATH"
Defaults        env_keep += "ARNOLD_PLUGIN_PATH"
Defaults        env_keep += "MTOA_EXTENIONS"
Defaults        env_keep += "PATH"
Defaults        env_keep += "LD_LIBRARY_PATH"
Defaults        env_keep += "solidangle_LICENSE"
Defaults        env_keep += "RLM_LICENSE

Running /bin/sh -c set i can see that none of my vars are being loaded

4

Silly question, but what are the settings you have in the ‘run as user’ section. There are some explicit ones for retaining the environment, and we might have had a bug in 8.0 which has been fixed in 8.1. I just want to make sure you have the ‘use sudo’ or the ‘preserve environment’ turned on before I start digging in.

If you want to hack around it temporarily, you can place the environment variables in the loader script for the Python Sandbox at “/opt/Thinkbox/Deadline8/bin/pythonsandbox”. Because the Python Sandbox is executed by the ‘run as user’ code, that shouldn’t be affected by the login process. You can also try setting them up in a script within “/etc/profile.d” since that would be executed by most of the login processes, but that’s machine-by-machine as well.

5

I fixed by re-installing and now run as root, rather than user. Might try to run as user again once our current project wraps up.

Thanks for the help