CONDA style MOOSE installation issue in HPC

[mdh23rct]

Dear all,
I have installed Conda MOOSE Environment in our HPC cluster. However, when I run the slurm script, it gives the error "error while loading shared libraries: libwaspcore.so.04: cannot open shared object file: No such file or directory"

I looked at the projects/moose/conda/wasp/ directory. I am not seeing any libwaspcore.so.04 file in the wasp folder. What I can do now?

During cloning and making the moose folder I did not see any error, though.

I would appreciate if you could manage time to reply.

Thanks.

[milljm]

While working within an HPC enclave, it is best to use that clusters vetted compiler stack, rather than install ours via Conda.

You should instead be following these instructions: https://mooseframework.inl.gov/getting_started/installation/hpc_install_moose.html

The error you are receiving is likely a result of building with one set of compilers while attempting to use another (HPC modules verses our Conda packages).

The location you are describing moose/conda/wasp/ is the location containing the recipes necessary to build the Conda moose-wasp package used for redistribution on our https://conda.software.inl.gov/public channel. Basically, nothing you need concern yourself with.

[mdh23rct]

@milljm I ran the slurm script you have suggested. Please have the slurm output showing a lot of information with the same error
"./recryss-opt: error while loading shared libraries: libwaspcore.so.04: cannot open shared object file: No such file or directory"

slurm-output.txt

Please help. Thanks.

[GiudGiud]

can you report the output of ldd recryss-opt

[milljm]

I would be interested in seeing ldd recryss-opt as well.

One glaring concern of mine, is that recryss-opt was built using Conda compilers, yet Conda is no where to be found in your SLURM batch environment right before the binary is run.

[GiudGiud]

One glaring concern of mine, is that recryss-opt was built using Conda compilers, yet Conda is no where to be found in your SLURM batch environment right before the binary is run.

yeah I agree.
Let's conda activate moose right before the srun comand if you are going to be using a conda-build on this cluster (not usually recommended)

[milljm]

I don't see conda anywhere in the output. Not in the env | sort, and not in PATH... I am not so sure a conda activate will work in our case now that I think about it.

Strangely, the only mentioning of Conda, is our public channel. Hmm... actually, I think that is being set by our diagnostic script.

@mdh23rct, if you can re-run the ./diagnostic.sh script manually, and report those results again, that may prove helpful. By manually, I mean, not via a SLURM job submission.