I gather you are using OMPI 2.x, yes? And you configured it --with-pmi=<slurm-pmi-lib>, then moved the executables/libs to your workstation?
I suppose I could state the obvious and say “don’t do that - just rebuild it”, and I fear that (after checking the 2.x code) you really have no choice. OMPI v3.0 will have a way around the problem, but not the 2.x series. > On Jun 22, 2017, at 8:04 AM, Michael Di Domenico <mdidomeni...@gmail.com> > wrote: > > On Thu, Jun 22, 2017 at 10:43 AM, John Hearns via users > <users@lists.open-mpi.org> wrote: >> Having had some problems with ssh launching (a few minutes ago) I can >> confirm that this works: >> >> --mca plm_rsh_agent "ssh -v" > > this doesn't do anything for me > > if i set OMPI_MCA_sec=^munge > > i can clear the mca_sec_munge error > > but the mca_pmix_pmix112 and opal_pmix_base_select errors still > exists. the plm_rsh_agent switch/env var doesn't seem to affect that > error > > down the road, i may still need the rsh_agent flag, but i think we're > still before that in the sequence of events > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/users _______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
