When using dpython, i can import a central library we use just fine:
import scl.deadline.startLauncher
but using the monitor via a slave script, it fails…:
2014-10-29 09:58:35: Running script StartDeadlineLauncher (\inferno2.scanlinevfxla.com\deadline\repository7\scripts\Slaves\StartDeadlineLauncher.py)
2014-10-29 09:58:35: Traceback (most recent call last):
2014-10-29 09:58:35: File “DeadlineUI\UI\Commands\ScriptCommands.py”, line 101, in InnerExecute
2014-10-29 09:58:35: PythonNetException: ImportError : No module named scl.deadline.startLauncher
2014-10-29 09:58:35: File “none”, line 13, in
Any ideas how i could troubleshoot this?
Seems like somehow the python environment in the monitor is cross loading some python 2.6 dlls…
2014-10-29 11:08:47: Running script StartDeadlineLauncher (\inferno2.scanlinevfxla.com\deadline\repository7\scripts\Slaves\StartDeadlineLauncher.py)
2014-10-29 11:08:47: Traceback (most recent call last):
2014-10-29 11:08:47: File “DeadlineUI\UI\Commands\ScriptCommands.py”, line 101, in InnerExecute
2014-10-29 11:08:47: PythonNetException: ImportError : Module use of python26.dll conflicts with this version of Python.
2014-10-29 11:08:47: File “none”, line 13, in
2014-10-29 11:08:47: File “c:\Program Files\Thinkbox\Deadline7\bin\lib\site-packages\sitecustomize.py”, line 97, in
2014-10-29 11:08:47: import socket
2014-10-29 11:08:47: File “C:\python26_64\Lib\socket.py”, line 46, in
2014-10-29 11:08:47: import _socket
Not sure why it would be loading from C:\python26_64. Have you tried printing out sys.path to see the current search paths that Deadline is using?
Yeah, our systems have python26 installed as standard, so python26 is in sys.path. Not sure why its in front of deadline’s own folders though…
Im evaluating a change to our sitecustomize package right now that strips all folders from sys.path that dont match the executable’s folder prefix, but that might have unintended consequences. Also weird why dpython works… in theory they are the same, no?
Reinstalling deadline client somehow fixed this. No clue why… The python26 folders now disappeared from the env.
Im gonna go take a crazy pill.
In beta 4, we changed how Deadline configures it’s python environment, but it required a reinstall of the client to include some modified python files. If this machine was previously upgraded using auto-upgrading, that would explain why the environment was messed up, and why a reinstall fixed it.
Cheers,
Ryan
Ah… Hm… Good point.
Ill do a quick sweep of the registry entries on the machines to see what was the last “proper” install, and make sure its of the latest build.