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<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e4:b9:7a:01:ec:11  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xef200000-ef220000 

*lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536**
**        inet 127.0.0.1  netmask 255.0.0.0**
**        inet6 ::1  prefixlen 128  scopeid 0x10<host>**
**        loop  txqueuelen 1000  (Boucle locale)**
**        RX packets 525941  bytes 859209091 (819.4 MiB)**
**        RX errors 0  dropped 0  overruns 0  frame 0**
**        TX packets 525941  bytes 859209091 (819.4 MiB)**
**        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0**
*
virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:2d:6f:8e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 76:f4:76:61:12:28  txqueuelen 1000  (Ethernet)
        RX packets 941959  bytes 1168504942 (1.0 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 491366  bytes 63144705 (60.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Le 28/01/2019 à 15:17, Gilles Gouaillardet a écrit :
> 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
> <mailto:patrick.be...@legi.grenoble-inp.fr>> wrote:
>
>     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 for out-of-band communications.
>     We require
>     at least one available network for out-of-band messaging.
>     --------------------------------------------------------------------------
>
>     OpenMPI is built localy with
>
>                     Open MPI: 3.1.3rc1
>       Open MPI repo revision: v3.1.2-78-gc8e9819
>       Configure command line: '--prefix=/opt/GCC73/openmpi31x'
>                               '--enable-mpirun-prefix-by-default'
>                               '--disable-dlopen'
>     '--enable-mca-no-build=openib'
>                               '--without-verbs' '--enable-mpi-cxx'
>                               '--without-slurm'
>     '--enable-mpi-thread-multiple'
>
>     I've tested some btl setup found with google but none solve the
>     problem.
>
>     bash-4.2$ mpirun -np 4 -mca btl ^tcp hostname
>
>     or
>
>     bash-4.2$ mpirun -np 4 -mca btl vader,self hostname
>
>     Sarting a wifi connection (when it is available):
>
>     bash-4.2$ mpirun -np 4 hostname
>     localhost.localdomain
>     localhost.localdomain
>     localhost.localdomain
>     localhost.localdomain
>
>     Any suggestion is welcome
>
>     Patrick
>
>
> _______________________________________________
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users


_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Reply via email to