Also, you will want to check that you have valid entries in
/etc/dat.conf. You might see the message you report if this is empty.
Jeff Squyres wrote:
Note that you still definitely need "self" in the BTL list. "self"
is the loopback device/btl (i.e., one MPI process sending to itself;
no
George is right that the error message either indicates that the
dlopen() of the udapl component is failing (which seems unlikely, or
you'd see errors when you run ompi_info -- we use the same exact code
to open components in ompi_info as we do in MPI processes), the udapl
BTL is electing n
Note that you still definitely need "self" in the BTL list. "self"
is the loopback device/btl (i.e., one MPI process sending to itself;
not sending to another process on the same host).
On Nov 1, 2007, at 3:52 PM, Jon Mason wrote:
On Wed, Oct 31, 2007 at 06:45:10PM -0400, Tim Prins wrote:
On Thu, Nov 01, 2007 at 07:41:33PM -0400, George Bosilca wrote:
> There are two things that are reflected in your email.
>
> 1. You can run Open MPI (or at least ompi_info) on the head node, and
> udapl is in the list of BTL. This means the head node has all
> libraries required to load udapl,
There are two things that are reflected in your email.
1. You can run Open MPI (or at least ompi_info) on the head node, and
udapl is in the list of BTL. This means the head node has all
libraries required to load udapl, and your LD_LIBRARY_PATH is
correctly configured on the head node.
2
On Wed, Oct 31, 2007 at 06:45:10PM -0400, Tim Prins wrote:
> Hi Jon,
>
> Just to make sure, running 'ompi_info' shows that you have the udapl btl
> installed?
Yes, I get the following:
# ompi_info | grep dapl
MCA btl: udapl (MCA v1.0, API v1.0, Component v1.2.5)
If I do not inc
Hi Jon,
Just to make sure, running 'ompi_info' shows that you have the udapl btl
installed?
Tim
On Wednesday 31 October 2007 06:11:39 pm Jon Mason wrote:
> I am having a bit of a problem getting udapl to work via mpirun (over
> open-mpi, obviously). I am running a basic pingpong test and I get
