Dear Henk,
could You please try the reverse and specifically select the pml, that would
adress the openib BTLs, by using:
mpirun -np $NSLOTS --mca pml ob1 $exe
Hope, this helps.
CU,
Rainer
On Mittwoch, 18. Juni 2008, SLIM H.A. wrote:
> Hi George
>
> I just tried that and got a different error
Hi George
I just tried that and got a different error message:
--
No available pml components were found!
This means that there are no components of this type installed on your
system or all the components reported that the
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of George Bosilca
> Sent: 18 June 2008 15:27
> To: Open MPI Users
> Subject: Re: [OMPI users] Error in mx_init message
>
> This is a different issue. On top of Myrinet, Open MPI suppo
Dear folks,
I would appreciate your help on the following:
I'm running a parallel CFD code on the Army Research Lab's MJM Linux
cluster, which uses Open-MPI. I've run the same code on other Linux
clusters that use MPICH2 and had never run into this problem.
I'm quite convinced that the bottlenec
This is a different issue. On top of Myrinet, Open MPI support two
nodes: cm and the others. Basically, the difference is how the card
will be used. If you only specify the btls then Open MPI will try to
initialize the CM PML and that's how this error message appears. If
you add OMPI_MCA_pm
I have OpenMPI-1.2.5 configured with myrinet and infiniband:
OMPI_MCA_btl=openib,self,sm
The job runs with the "error" message
"Error in mx_init (error MX driver not loaded.)"
which makes sense in itself as there is no myrinet card on the node.
Is it correct to assume that the ib interconnec
Thanks Brian -- I've updated the FAQ.
On Jun 18, 2008, at 9:56 AM, Brian W. Barrett wrote:
Thanks for adding the section, but the information contained within
is wrong (as was the information in this e-mail thread). OS X
essentially *always* adds a -rpath to both executables depending on
Thanks for adding the section, but the information contained within is
wrong (as was the information in this e-mail thread). OS X essentially
*always* adds a -rpath to both executables depending on libraries and
libraries depending on other libraries. There is no need to set
LD_LIBRARY_PATH,
FWIW, I added this issue to the FAQ under the "OS X" section to make
it a little easier to find.
On Jun 17, 2008, at 5:17 PM, Jeff Squyres wrote:
Sorry for not replying earlier -- glad you figured it out.
Yes, if you didn't also reset the LIBRARY_PATH, the "wrong" libmpi
(and friends) will
