Thanks.
That's exactly the problem. When add prefix to the mpirun command,
everything goes fine.
- Zehan Cui
On Fri, Jun 14, 2013 at 10:25 PM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> Check the PATH you get when you run non-interactively on the remote
> machine:
>
> ssh gnode10
Check the PATH you get when you run non-interactively on the remote machine:
ssh gnode100 env | grep PATH
On Jun 14, 2013, at 10:09 AM, Zehan Cui wrote:
> I think the PATH setting is ok. I forgot to mention that it run well on local
> machine.
>
> The PATH setting on the local machine is
>
I think the PATH setting is ok. I forgot to mention that it run well on
local machine.
The PATH setting on the local machine is
[cmy@gLoginNode1 ~]$ echo $PATH
/home/cmy/clc/benchmarks/nasm-2.09.10:*/home3/cmy/czh/opt/ompi-1.7.1/bin/*
:/home3/cmy/czh/opt/autoconf-2.69/bin/:/home3/cmy/czh/opt/mvap
You aren't setting the path correctly on your backend machines, and so they are
picking up an older version of OMPI.
On Jun 14, 2013, at 2:08 AM, Zehan Cui wrote:
> Hi,
>
> I have just install OpenMPI-1.7.1 and cannot get it running.
>
> Here is the error messages:
>
> [cmy@gLoginNode1 test_
Hi,
I have just install OpenMPI-1.7.1 and cannot get it running.
Here is the error messages:
[cmy@gLoginNode1 test_nbc]$ mpirun -n 4 -host gnode100 ./hello
[gnode100:31789] Error: unknown option "--tree-spawn"
input in flex scanner failed
[gLoginNode1:14920] [[62542,0],0] ORTE_ERROR_LOG: A messa