I’m using a build of OpenMPI provided by a third party.
--
Gary Jackson, Ph.D.
Johns Hopkins University Applied Physics Laboratory
On 8/21/17, 8:04 PM, "users on behalf of Gilles Gouaillardet"
<users-boun...@lists.open-mpi.org on behalf of gil...@rist.or.jp> wrote:
Gary,
one option (as mentioned in the error message) is to configure Open MPI
with --enable-orterun-prefix-by-default.
this will force the build process to use rpath, so you do not have to
set LD_LIBRARY_PATH
this is the easiest option, but cannot be used if you plan to relocate
the Open MPI installation directory.
an other option is to use a wrapper for orted.
mpirun --mca orte_launch_agent /.../myorted ...
where myorted is a script that looks like
#!/bin/sh
export LD_LIBRARY_PATH=...
exec /.../bin/orted "$@"
you can make this setting system-wide by adding the following line to
/.../etc/openmpi-mca-params.conf
orte_launch_agent = /.../myorted
Cheers,
Gilles
On 8/22/2017 1:06 AM, Jackson, Gary L. wrote:
>
> I’m using a binary distribution of OpenMPI 1.10.2. As linked, it
> requires certain shared libraries outside of OpenMPI for orted itself
> to start. So, passing in LD_LIBRARY_PATH with the “-x” flag to mpirun
> doesn’t do anything:
>
> $ mpirun –hostfile ${HOSTFILE} -N 1 -n 2 -x LD_LIBRARY_PATH hostname
>
> /path/to/orted: error while loading shared libraries: LIBRARY.so:
> cannot open shared object file: No such file or directory
>
> --------------------------------------------------------------------------
>
> ORTE was unable to reliably start one or more daemons.
>
> This usually is caused by:
>
> * not finding the required libraries and/or binaries on
>
> one or more nodes. Please check your PATH and LD_LIBRARY_PATH
>
> settings, or configure OMPI with --enable-orterun-prefix-by-default
>
> * lack of authority to execute on one or more specified nodes.
>
> Please verify your allocation and authorities.
>
> * the inability to write startup files into /tmp
> (--tmpdir/orte_tmpdir_base).
>
> Please check with your sys admin to determine the correct location to use.
>
> * compilation of the orted with dynamic libraries when static are required
>
> (e.g., on Cray). Please check your configure cmd line and consider using
>
> one of the contrib/platform definitions for your system type.
>
> * an inability to create a connection back to mpirun due to a
>
> lack of common network interfaces and/or no route found between
>
> them. Please check network connectivity (including firewalls
>
> and network routing requirements).
>
> --------------------------------------------------------------------------
>
> How do I get around this cleanly? This works just fine when I set
> LD_LIBRARY_PATH in my .bashrc, but I’d rather not pollute that if I
> can avoid it.
>
> --
>
> Gary Jackson, Ph.D.
>
> Johns Hopkins University Applied Physics Laboratory
>
>
>
> _______________________________________________
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
