Sergei,
thanks for confirming you are now able to use Open MPI
fwiw, orted is remotely started by the selected plm component.
it can be ssh if you run without a batch manager, the tm interface if
PBS/torque, srun if slurm, etc ...
that should explain why exporting PATH and LD_LIBRARY_PATH is not enough
in your environment,
not to mention your .bashrc or equivalent might reset/unset
Cheers,
Gilles
----- Original Message -----
Hi Gilles!
this looks like a very different issue, orted cannot be remotely
started.
...
a better option (as long as you do not plan to relocate Open MPI
install dir) is to configure with
--enable-mpirun-prefix-by-default
Yes, that's was a problem with orted.
I checked PATH and LD_LIBRARY_PATH variables and both are specified,
but it was not enough!
So I added --enable-mpirun-prefix-by-default to configure and even
when --prefix isn't specified the recompiled version woks properly.
When Ethernet transfer is used, all works both with and without --
enable-mpirun-prefix-by-default.
Thank you!
Best regards,
Sergei.
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
