-
Notifications
You must be signed in to change notification settings - Fork 1
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
Failed .cerise/ environment setup on remote HPC resource #81
Comments
Some server logs would be really useful for this. If you have the container still, you can get them using |
This is the cerise_backend log from the last run using the cerise-mdstudio-lisa specialization:
|
Uh oh, this is not good. You're using the latest develop Cerise, and the specialisation hasn't been updated to that yet. The new version has a It looks like the problem is in the cerise-mdstudio-lisa Dockerfile, it says |
I see, makes sense, I will update the version |
Updated the docker file and rerun a workflow with the newly build docker image.
The api is indeed not build, no conda installation. |
That looks like it could be that Lisa has the very latest version of Slurm, and that Xenon 1 doesn't support it. So I guess it'll have to wait for the new Cerise with Cerulean... |
Lisa is running Slurm 18.08, so indeed pretty new. Cerulean isn't tested with it yet either, but I'll add it. |
The current Cerulean works fine with 18.08, and this will be backed up by tests in the next version. |
I'm experiencing incomplete setup of remote .cerise/ environments on GT and LISA HPC resources.
For GT the .cerise/ directory and all of the files in it where copied to the remote resource but the setup procedure failed at the miniconda stage. Miniconda was downloaded and installed but the cerise virtual env was not created. After running the respective install script manually the environment was created successfully and MD jobs could be launched by lie_md.
For LISA only the .cerise/api and .cerise/jobs directories where created without any files in them. The system hanged in this state indefinite. I tried a few times always with the same result.
The text was updated successfully, but these errors were encountered: