We already do that as a check, but it came after the 1.6 series - and so you
get the old error message if you mix with the 1.6 series or older versions.
> On May 16, 2016, at 8:22 AM, Gilles Gouaillardet
> wrote:
>
> or this could be caused by a firewall ...
> v1.10 and earlier uses tcp for o
or this could be caused by a firewall ...
v1.10 and earlier uses tcp for oob,
from v2.x, unix sockets are used
detecting consistent version is a good idea,
printing them (mpirun, orted and a.out) can be a first step.
my idea is
mpirun invokes orted with '--ompi_version=x.y.z'
orted checks it is
Ralph Castain writes:
> This usually indicates that the remote process is using a different OMPI
> version. You might check to ensure that the paths on the remote nodes are
> correct.
That seems quite a common problem with non-obvious failure modes.
Is it not possible to have a mechanism that c
/2016/05/29160.php>
* *Previous message:* Gus Correa: "Re: [OMPI users] No core dump in
some cases"
<https://www.open-mpi.org/community/lists/users/2016/05/29158.php>
* *In reply to:* lzfneu: "[OMPI users] Question about mpirun
mca_oob_tcp_recv_handler error."
path and add
it to .bashcr file. However, the results with no effect.
[user@localhost ~]$ which mpirun/usr/lib64/openmpi/bin/mpirun
Any idea and thanks in advance!
Subject: Re: [OMPI users] Question about mpirun mca_oob_tcp_recv_handler error.
From: Ralph Castain (rhc_at_[hidden])
Date: 2016-05-10
This usually indicates that the remote process is using a different OMPI
version. You might check to ensure that the paths on the remote nodes are
correct.
On Tue, May 10, 2016 at 8:46 AM, lzfneu wrote:
> Hi everyone,
>
> I have a problem to consult you, when I cd to the /examples folder
> cont
Hi everyone,
I have a problem to consult you, when I cd to the /examples folder contained in
the openmpi-1.8.4 package, and test the hello_c example program with mpirun
command errors occured:
Here are the command and the error messages in details:
[user@localhost examples]$ mpirun -np 2 hello
