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

hydra: ssh is used as a launcher on a single node #7186

Open
orcunyildiz opened this issue Oct 22, 2024 · 0 comments
Open

hydra: ssh is used as a launcher on a single node #7186

orcunyildiz opened this issue Oct 22, 2024 · 0 comments

Comments

@orcunyildiz
Copy link

I'm running mpich on a single node on the LCRC Swing cluster, but the launcher still picks up the ssh instead of fork. Please ignore the OpenSSL error, which is due to mismatch in OpenSSL versions between my Spack environment and Swing.

oyildiz@gpu6: $ mpiexec -n 12 ./lmp -in ./in.relax
OpenSSL version mismatch. Built against 30000020, you have 30100030
[mpiexec@gpu6] ui_cmd_cb (mpiexec/pmiserv_pmci.c:51): Launch proxy failed.
[mpiexec@gpu6] HYDT_dmxu_poll_wait_for_event (lib/tools/demux/demux_poll.c:76): callback returned error status
[mpiexec@gpu6] HYD_pmci_wait_for_completion (mpiexec/pmiserv_pmci.c:181): error waiting for event
[mpiexec@gpu6] main (mpiexec/mpiexec.c:252): process manager error waiting for completion

Here is the launcher details from the verbose mode output:

[mpiexec@gpu6] Launch arguments: /bin/ssh -x gpu6.lcrc.anl.gov "/lcrc/project/PEDAL/oyildiz/software/spack/var/spack/environments/accelerate-spack-env-mpi-cuda/.spack-env/view/bin/hydra_pmi_proxy" --control-port gpu6:44647 --debug --rmk pbs --launcher ssh --demux poll --pgid 0 --retries 10 --usize -2 --pmi-port 0 --gpus-per-proc -2 --gpu-subdevs-per-proc -2 --proxy-id 0 
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

1 participant