You might also want to set up your shell startup files on each machine to reflect the proper PATH and LD_LIBRARY_PATH. E.g., if you have a different .bashrc on each machine, just have it set PATH and LD_LIBARY_PATH properly *for that machine*.
To be clear: it's usually easiest to install OMPI to the same prefix on every machine, but there's no technical requirement from OMPI to do so. On Jun 18, 2012, at 10:00 AM, Ralph Castain wrote: > Try adding "-x LD_LIBRARY_PATH=<remote-prefix>" to your mpirun cmd line > > > On Jun 18, 2012, at 7:11 AM, Harald Servat wrote: > >> Hello list, >> >> I'd like to use OpenMPI to execute an MPI application in two different >> machines. >> >> Up to now, I've configured and installed OpenMPI 1.6 in my two systems >> (each on a different directory). When I execute binaries within a system >> (in any) the application works well. However when I try to execute in >> the two systems, it does not work, in fact it complains it cannot find >> "orted". This is the command I try to run and its output >> >> # $HOME/aplic/openmpi/1.6/bin/mpirun -display-map --machinefile hosts >> -np 2 /bin/date >> >> ======================== JOB MAP ======================== >> >> Data for node: M1 Num procs: 1 >> Process OMPI jobid: [6021,1] Process rank: 0 >> >> Data for node: M2 Num procs: 1 >> Process OMPI jobid: [6021,1] Process rank: 1 >> >> ============================================================= >> bash: /home/harald/aplic/openmpi/1.6/bin/orted: El fitxer o directori no >> existeix >> -------------------------------------------------------------------------- >> A daemon (pid 19598) died unexpectedly with status 127 while attempting >> to launch so we are aborting. >> >> There may be more information reported by the environment (see above). >> >> This may be because the daemon was unable to find all the needed shared >> libraries on the remote node. You may set your LD_LIBRARY_PATH to have >> the >> location of the shared libraries on the remote nodes and this will >> automatically be forwarded to the remote nodes. >> -------------------------------------------------------------------------- >> -------------------------------------------------------------------------- >> mpirun noticed that the job aborted, but has no info as to the process >> that caused that situation. >> -------------------------------------------------------------------------- >> >> My guess is that the spawn process cannot find orted in M2 because the >> installation prefix of M1 and M2 differ. Is my guess correct? As I >> cannot change the prefix of the two installation, how can I tell mpirun >> to look for orted in a different place? After looking at the >> documentation, I've tried with --prefix and --launch-agent without >> success. >> >> Thank you very much in advance. >> >> >> >> >> >> WARNING / LEGAL TEXT: This message is intended only for the use of the >> individual or entity to which it is addressed and may contain >> information which is privileged, confidential, proprietary, or exempt >> from disclosure under applicable law. If you are not the intended >> recipient or the person responsible for delivering the message to the >> intended recipient, you are strictly prohibited from disclosing, >> distributing, copying, or in any way using this message. If you have >> received this communication in error, please notify the sender and >> destroy and delete any copies you may have received. >> >> http://www.bsc.es/disclaimer >> _______________________________________________ >> users mailing list >> us...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/users > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
