Francesco,
We use modules (http://modules.sourceforge.net/) to manage 14 different
OpenMPI versions on the same cluster, along with their associated
applications. This is a nice way to establish dependancies between apps
and libs and keep things organized.
Good luck.
--andy
$ module avail
Hello all,
We recently applied the latest RedHat update (/etc/redhat-release says
"Red Hat Enterprise Linux WS release 4 (Nahant Update 7)") to our cluster,
and now codes that use IB seg fault.
We have tried multiple versions of OpenMPI and PGI and GNU compilers. We
have compiled with --memory-
As I mentioned it might be, it was a local issue.
The lesson is that one should be very careful about OFED versions and
cleanliness. :)
--andy
On Mon, 25 Aug 2008, Andrew J Caird wrote:
Hello all,
We recently applied the latest RedHat update (/etc/redhat-release says
"Red Hat Enter
FWIW, It compiles with PGI 7.2 on RHEL4U7
[acaird@nyx-login1 ~]$ ompi_info | grep "compiler abs"
C compiler absolute: /usr/caen/pgi-7.2/linux86-64/7.2-1/bin/pgcc
C++ compiler absolute: /usr/caen/pgi-7.2/linux86-64/7.2-1/bin/pgCC
Fortran77 compiler abs: /usr/caen/pgi-7.2/linux86-64/7.2
This took a long time for me to get to, but once I did, what I found was
that the closest thing to working for the PGI compilers with OpenMPI is
this command:
mpirun --debugger "pgdbg @mpirun@ @mpirun_args@" --debug -np 2 ./cpi
It appears to work, that is, you can select a process with the
Hello,
I have a short code segment that, when compiled with mpiCC fails
at run-time with the error:
C++ runtime abort: internal error: static object marked for
destruction more than once
If I compile the same code with mpicc, it works fine. If I
compile the same code with LAM's mpiCC it
Hello,
I looked into this a few months back, although we have had OK
luck using LAM with R/MPI. I emailed the author of R/MPI, Dr.
Hao Yu and his answer was:
Date: Mon, 25 Sep 2006 21:57:40 -0500
From: Hao Yu
To: "Caird, Andrew J"
Subject: Re: Rmpi and OpenMPI?
Hi Andy,
Sorry for my sl
You can also usually watch the counters on the IB cards and
Ethernet cards. For programs that have a lot of communication
between nodes it is quickly obvious which network you're using.
The IB card monitoring is driver specific, but you should have
some tools for this. For Ethernet you can
