Thanks, that actually worked!

Best,
Udayanga


On Mon, Jan 7, 2019 at 8:23 AM Bennet Fauber <ben...@umich.edu> wrote:

> Used to be that you could put default MCA settings in
> OMPI_ROOT/etc/openmpi-mca-params.conf.
>
>     btl_openib_allow_ib=1
>
> You could try that.
>
> -- bennet
>
>
>
> On Mon, Jan 7, 2019 at 8:16 AM Udayanga Wickramasinghe <uswic...@iu.edu>
> wrote:
> >
> > Hi Salim,
> > Thank you. Yeah, I noticed warnings would vanish by turning on
> btl_openib_allow_ib -- but since this is quite annoying I am wondering if
> there is any other way to suppress this by configuration.
> >
> > Best,
> > Udayanga
> >
> > On Mon, Jan 7, 2019 at 7:33 AM Salim Jamal-Eddine <
> salim.jamal-edd...@lau.edu.lb> wrote:
> >>
> >> Hi Udayanga,
> >>
> >>
> >>
> >> I had the same issue, the default behavior of OpenMpi4.0.0 is to use
> UCX.. add “–mca btl_openib_allow_ib 1” and everything should be fine.
> >>
> >>
> >>
> >> Regards,
> >>
> >>
> >>
> >>
> >>
> >> Salim Jamal-Eddine
> >>
> >> Lead Engineering Labs Supervisor
> >> Industrial & Mechanical Engineering Department, Byblos Campus
> >> School of Engineering
> >>
> >> Office: +961 1 786456 ext. 2899
> >>
> >> f
> >>
> >> SOE
> >>
> >>
> >>
> >> Beirut | Byblos | New York
> >>
> >> f
> >>
> >> in
> >>
> >> t
> >>
> >> ig
> >>
> >> ________________________________
> >>
> >>
> >>
> >> From: users <users-boun...@lists.open-mpi.org> On Behalf Of Udayanga
> Wickramasinghe
> >> Sent: Monday, January 07, 2019 1:03 PM
> >> To: Open MPI Users <us...@open-mpi.org>
> >> Cc: Open MPI Users <users@lists.open-mpi.org>
> >> Subject: [OMPI users] A strange warning on Cray XC with Opemmpi-4.00
> >>
> >>
> >>
> >> Hi,
> >>
> >> I upgraded my open-mpi version to 4.00 on a Cray Aries cluster
> (GNI/uGNI). Every time I run mpi, I get the following warning. Is there any
> way to suppress this message? I am not seeing this in 3.1.3 version of
> open-mpi. Any idea why openfabrics device is getting initialized when cray
> GNI transport is actively used? (i.e. looks like it is related to UCX, but
> I assume this could potentially be a configuration issue even though GNI
> transport/btl seems to get detected correctly and works by default without
> any explicit --mca parameters)
> >>
> >>
> >>
> >>
> >>
> >> By default, for Open MPI 4.0 and later, infiniband ports on a device
> >>
> >> are not used by default.  The intent is to use UCX for these devices.
> >>
> >> You can override this policy by setting the btl_openib_allow_ib MCA
> parameter
> >>
> >> to true.
> >>
> >>
> >>
> >>   Local host:              nid00301
> >>
> >>   Local adapter:           ibgni
> >>
> >>   Local port:              1
> >>
> >>
> >>
> >>
> --------------------------------------------------------------------------
> >>
> >>
> --------------------------------------------------------------------------
> >>
> >> WARNING: There was an error initializing an OpenFabrics device.
> >>
> >>
> >>
> >>   Local host:   nid00300
> >>
> >>   Local device: ibgni
> >>
> >>
> >>
> >> ... [program output]
> >>
> >> ... [program output]
> >>
> >> ...
> >>
> >>
> >>
> >> [login1:02032] 3 more processes have sent help message
> help-mpi-btl-openib.txt / ib port not selected
> >>
> >> [login1:02032] Set MCA parameter "orte_base_help_aggregate" to 0 to see
> all help / error messages
> >>
> >> [login1:02032] 3 more processes have sent help message
> help-mpi-btl-openib.txt / error in device init
> >>
> >>
> >>
> >> Thanks,
> >> Udayanga
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
> _______________________________________________
> 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