The problem is in your cmd line:
mpirun --np 2 --nolocal APPNAME
You forgot to include a -hostfile or -host option, so OMPI only knows
about your local node - which you told it not to use.
Provide a hostfile, or specify a set of hosts with -host, and it
should work fine.
Ralph
On Fe
Hi!
I'm using OpenMPI 1.3 on two nodes connected with Infiniband; i'm using
Gentoo Linux x86_64.
I've noticed that before any application starts there is a variable amount
of time (around 3.5 seconds) in which the terminal just hangs with no output
and then the application starts and works well.
On Feb 24, 2009, at 4:43 AM, Olaf Lenz wrote:
We've talked about similar errors before; I thought that the issue
was caused by the Python front-end calling dlopen() to manually
open the libmpi.so library. Is that the cause in your scenario?
Not really. We have written a shared library _esp
Hello all,
I am sorry to ask what is probably a newbie question, I have searched the
archives but am probably not using the proper key word to locate.
I am working on an atmospheric model which uses openmpi/openrte. I have two
nodes setup but the model only runs on one node.
I can use mpi
Hi.Due that xgrid support is broken at the moment in 1.3, I am trying to
install 1.2.9 in a xserve cluster.
I am using the gcc compilers downloaded from http://hpc.sourceforge.net/.
To be sure to not mixing compiler I am using the following configure
./configure --prefix=/opt/openmpi CC=/usr/lo
On Feb 24, 2009, at 1:07 PM, Jeff Squyres wrote:
The minimpi(.py) Python module loads the minimpiext(.c) module and
calls
its minimpiext.init() method (defined in minimpiext.c) which in turn
calls MPI_Init(). "minimpiext.c" is linked against libmpi. Libmpi is
loaded as soon as Python evaluates
On Feb 24, 2009, at 11:32 AM, > wrote:
The minimpi(.py) Python module loads the minimpiext(.c) module and
calls
its minimpiext.init() method (defined in minimpiext.c) which in turn
calls MPI_Init(). "minimpiext.c" is linked against libmpi. Libmpi is
loaded as soon as Python evaluates "import
I don't know for sure, but I don't think that anyone has tried
building with mingw.
Native Windows compiler support is available on the Open MPI
development trunk; it should be coming to a real release soon.
On Feb 24, 2009, at 9:28 AM, j artieda wrote:
I would like to know if is possible
> > Upon further investigation, it seems to be a problem similar to
this:
> > http://www.open-mpi.org/community/lists/devel/2005/09/0359.php
> > The dynamic parts of the library are however no more linked against
> > their frameworks.
> I looked at your tarball -- I don't know anything about Pytho
On Feb 23, 2009, at 8:59 PM, Jeff Squyres wrote:
Err... I'm a little confused. We've been emailing about this exact
issue for a week or two (off list); you just re-started the
conversation from the beginning, moved it to the user's list, and
dropped all the CC's (which include several peop
Hi!
Only now I have realized that there is another mailing which seems to
describe pretty much the same problem as I have (Subject: "Problems in
1.3..."). I wonder why I haven't seen it when I had searched for the bug
before, and I'm sorry if I have started the subject all over again.
I will
On Feb 24, 2009, at 10:29 AM, wrote:
I have a runtime-linking problem with MPI 1.3 that is very similar.
We apply MPI in a Python-based framework. For some platforms we use a
patched Python version that does the MPI_Init() call.
On some machines we use an unmodified Python with a small module
Generally, about 30 minutes. Just download the tarball and expand it,
then a quick configure/build and you are done
On Feb 24, 2009, at 1:31 AM, Ted Yu wrote:
We already have open-mpi installed in one of our clusters (because
it came with it). How long do you estimate it will take to insta
Hello,
I have a runtime-linking problem with MPI 1.3 that is very similar.
We apply MPI in a Python-based framework. For some platforms we use a
patched Python version that does the MPI_Init() call.
On some machines we use an unmodified Python with a small module
(minimpi) that cares for the MPI_
I would like to know if is possible to compile openmpi using msys-mingw
I have seen in the mailing list archives that some people have tried to compile
it with cygwin but It's not clear if they have succeeded.
I have tried to compile using a simple
./configure
make
but it fails with some redec
Hello,
I'm new to MPI, so I'm going to explain my problem in detail
I'm trying to compile a simple application using mpicc (on SUSE 10.0)
and run it - compilation passes well, but mpirun is the problem.
So, let's say the program is called 1.c, I tried the following:
mpicc -o 1 1.c
(and, just fo
Dear all:
Because I am new to this list, I would like to introduce myself as
Thomas Exner and please excuse silly questions, because I am only a chemist.
And now my problem, with which I am fiddling around for almost a week: I
try to use gamess with openmpi on infiniband. There is a good
descript
Hi!
And now for the actual mailing.
Jeff Squyres wrote:
We've talked about similar errors before; I thought that the issue was
caused by the Python front-end calling dlopen() to manually open the
libmpi.so library. Is that the cause in your scenario?
Not really. We have written a shared lib
Hi!
Jeff Squyres wrote:
On Feb 23, 2009, at 10:44 AM, Olaf Lenz wrote:
Good idea. How about a compromise -- I'll change the "Bug tracking"
link on the ompi web site to point to an intermediate page on the ompi
web site itself with some explanation text and links to both the
"getting help" pa
We already have open-mpi installed in one of our clusters (because it came with
it). How long do you estimate it will take to install open-mpi to another
linux cluster (red hat 9) that does not have open-mpi preinstalled?
Ted
20 matches
Mail list logo
