This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
You should not be invoking orted manually -- getting errors when you
invoke orted manually is probably to be expected.
Can you answer the questions from my original mail? Thanks.
On Mar 27, 2009, at 6:29 PM, Russell McQueeney wrote:
> Jeff Squyres wrote:
> > Hmm -- puzzling -- the error file you sent shows the following:
> > bash: /opt/openmpi/orted: No such file or directory
> > But that shouldn't happen; according to your config.log, you
> > with a prefix of /opt/openmpi, so Open MPI should be looking for
> > in /opt/openmpi/bin/orted.
> > You said that the command was
> >> command = mpirun --hostfile hostfile -np 2 echo `uname -a`
> > Is there any chance that you ran with mpirun's absolute filename,
> > as:
> > /opt/openmpi/bin/mpirun --hostfile hostfile -np 2 echo `uname -a`
> > Or do you have any aliases involved? I can't imagine how you're
> > getting that error message -- Open MPI should never use a full path
> > name for orted unless you specified --prefix on the mpirun command
> > line (which you didn't), or youused a full path name for mpirun
> > it looks like you didn't, and even if you did use
> > /opt/openmpi/bin/mpirun, it should use that path to look for
> > /opt/openmpi/bin/orted on the other node). Otherwise, Open MPI
> > on the PATH set in your shell startup files on remote nodes to find
> > the orted.
> > This is very odd -- can you look at the exact command that is being
> > executed on the remote node?