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

mpiexec segfaults immediately on moose-dev docker image #28815

Open
nietzscheanmonkey opened this issue Oct 9, 2024 · 2 comments
Open

mpiexec segfaults immediately on moose-dev docker image #28815

nietzscheanmonkey opened this issue Oct 9, 2024 · 2 comments
Labels
P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.

Comments

@nietzscheanmonkey
Copy link

Bug Description

mpiexec appears to be completely broken on the Docker image for moose-dev. It segfaults immediately upon running, even without any custom operations to the container.

Best guess is that its not linked properly -- running ldd $(which mpiexec) shows less libraries than expected.

Steps to Reproduce

You can test this yourself with:

podman(or docker) run -it idaholab/moose-dev:latest
mpiexec

Which will immediately report a segfault.

Impact

High, makes mpi usage on image impossible

[Optional] Diagnostics

No response

@nietzscheanmonkey nietzscheanmonkey added P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations. labels Oct 9, 2024
@milljm
Copy link
Member

milljm commented Oct 9, 2024

Possibly related in the following discussion: #28798

@milljm
Copy link
Member

milljm commented Oct 10, 2024

This is weird behavior. I can reproduce what you are describing, but when I actually go to use MPI, it works fine.

moose-dev-mpich-x86_64:28a1964 [root@c9f7e3a4d390: / ]
# mpiexec
Segmentation fault
moose-dev-mpich-x86_64:28a1964 [root@c9f7e3a4d390: / ]
# mpiexec -n 2 echo hello
hello
hello

There is a new issue with some support packages not being initialized properly (like yaml). In order to run make properly in /projects/moose/test, I have to first deactivate the environment, and then re-activate it:

conda deactivate
conda activate moose
cd /projects/moose/test
make -j 3
./run_tests -j 3

and then everything works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.
Projects
None yet
Development

No branches or pull requests

2 participants