Thanks Gilles for this work around. And thanks to OpenMPI developpers
for this responsiveness to quickly correct the problem too.
I'll build and deploy this new version for the users as soon as I'm back
to the laboratory.
Patrick
Le 29/01/2019 à 06:48, Gilles Gouaillardet a écrit :
> Patrick,
>
Patrick,
I double checked the code, and indeed, mpirun should have automatically
felt back
on the loopback interface (and mpirun should have worked)
The virbr0 interface prevented that and this is a bug I fixed in
https://github.com/open-mpi/ompi/pull/6315
Future releases of Open MPI
Patrick,
The root cause is we do not include the localhost interface by default
for OOB communications.
You should be able to run with
mpirun --mca oob_tcp_if_include lo -np 4 hostname
Cheers,
Gilles
On 1/28/2019 11:02 PM, Patrick Bégou wrote:
Hi,
I fall in a strange problem with
Hi Gilles,
localhost is available in the state where the problem occurs. I discover
suddently this mpi trouble yesterday as I was working in the train...
otherwise I was always connected to the net at home (wifi) or at the
laboratory (wired)
bash-4.2$ ifconfig
enp0s31f6: flags=4099 mtu 1500
Patrick,
Does “no network is available” means the lo interface (localhost 127.0.0.1)
is not even available ?
Cheers,
Gilles
On Monday, January 28, 2019, Patrick Bégou <
patrick.be...@legi.grenoble-inp.fr> wrote:
> Hi,
>
> I fall in a strange problem with OpenMPI 3.1 installed on a CentOS7
>
Hi,
I fall in a strange problem with OpenMPI 3.1 installed on a CentOS7
laptop. If no network is available I cannot launch a local mpi job on
the laptop:
bash-4.2$ mpirun -np 4 hostname
--
No network interfaces were found
