Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Env variable not set - REZ2_DEFAULT_VERSION #153

Open
szuhow opened this issue May 9, 2024 · 2 comments
Open

Env variable not set - REZ2_DEFAULT_VERSION #153

szuhow opened this issue May 9, 2024 · 2 comments

Comments

@szuhow
Copy link

szuhow commented May 9, 2024

I have working moonray on my Centos 7 (in local rez) and commands moonray, moonray_gui, hd_usd2rdl... are working good, but i have issue with hd_render, as there is error as below:

Hydra setup time = 00:00:00.107
Performing remote REZ resolve
2024-05-09T16:26:53.639482 W client[96252]:140473516571008: [d2835181-4efc-43cb-a34c-7f19f93375b7]: {warnBadConfigVal} In config for mcrt: item environment should be an object
2024-05-09T16:26:53.639860 E client[96252]:140473516571008: [d2835181-4efc-43cb-a34c-7f19f93375b7]: {RezSetupFail} [ rez2] Failed to setup rez environment for mcrt : Environment variable REZ2_DEFAULT_VERSION is not set
Error: Failed to create an Arras session: Failed to create local session :Environment variable REZ2_DEFAULT_VERSION is not set

I did not have this issue on dockerized moonray, but when pulled with dependencies from container to host, there is issue as above. How to resolve that?

Best,
R

@rgwilson68
Copy link
Contributor

HdMoonray looks at the current Rez environment to check all the required packages are present. It expects REZ_MCRT_COMPUTATION_VERSION, REZ_ARRAS4_CORE_VERSION and REZ_MOONRAY_VERSION to all have values. If the env is partially complete, it will try to run rez-env to create a complete env : it looks like this is what is happening in your case. This has some dependencies on the DreamWorks environment, though, so it might not work for you.

It should work using Rez if you make sure the mcrt_computation, arras4_core, moonray and moonshine are all in your Rez environment before running hd_render. Then it should run without trying to make a new environment, so you won't see the message "Performing remote REZ resolve"

@szuhow
Copy link
Author

szuhow commented May 15, 2024

Thank you for complete answer - unsetting REZ_MOONRAY_VERSION helped me for that. It worked as separated environment but not as expected with Houdini rez'd environemnt - so I compiled Moonray against Houdini 20 as instructed in adro79#2 (with some changes, like increased version of Embree, and building in Centos 7 container, not Rocky Linux). After all operations Houdini has Moonray viewport in Solaris - and it is working. Hovewer, when I want to use hd_render/hd_usd2rdl in terminal, I have error:

Could not find platform independent libraries
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to [:<exec_prefix>]
Python path configuration:
PYTHONHOME = (not set)
PYTHONPATH = '/opt/rez_packages/demeter/0.1.2'
program name = 'python3'
isolated = 0
environment = 1
user site = 1
import site = 1
sys._base_executable = '/usr/bin/python3'
sys.base_prefix = '/home/prisms/builder-new/WeeklyDevToolsHEAD/dev_tools/src/python/python-3.10/prefix-py3.10'
sys.base_exec_prefix = '/home/prisms/builder-new/WeeklyDevToolsHEAD/dev_tools/src/python/python-3.10/prefix-py3.10'
sys.platlibdir = 'lib'
sys.executable = '/usr/bin/python3'
sys.prefix = '/home/prisms/builder-new/WeeklyDevToolsHEAD/dev_tools/src/python/python-3.10/prefix-py3.10'
sys.exec_prefix = '/home/prisms/builder-new/WeeklyDevToolsHEAD/dev_tools/src/python/python-3.10/prefix-py3.10'
sys.path = [
'/opt/rez_packages/demeter/0.1.2',
'/home/prisms/builder-new/WeeklyDevToolsHEAD/dev_tools/src/python/python-3.10/prefix-py3.10/lib/python310.zip',
'/home/prisms/builder-new/WeeklyDevToolsHEAD/dev_tools/src/python/python-3.10/prefix-py3.10/lib/python3.10',
'/home/prisms/builder-new/WeeklyDevToolsHEAD/dev_tools/src/python/python-3.10/prefix-py3.10/lib/lib-dynload',
]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007f626ef2c9c0 (most recent call first):

What could be reason for that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants