Hello. This may be a usage issue, but we did not have this problem with
version 1.0.2.
When starting a parallel job (using TCP) with mpirun, the following
message is repeated many times:
[devi01:24440] mca_oob_tcp_accept: accept() failed with errno 9.
[devi01:24440] mca_oob_tcp_accept: acc
Michael,
Hello. Thanks for the response. We do clean configures and makes under
/tmp, and install in a completely separate area so I don't see how
anything from 1.0.2 could be left over in the 1.1 installation. We
aren't installing 1.1 over 1.0.2. 1.1 is configured, built, and
installed
are in PATH or LD_LIBRARY_PATH or whatever environment
variable your compiler uses than things could be interesting (Intel
compiler using FPATH for include files).
Neither area was in the PATH, etc.
Michael
On Jun 26, 2006, at 6:28 PM, Patrick Jessee wrote:
Michael,
Hello
Hello. I've tracked down the source of the previously reported startup
problem with Openmpi 1.1. On startup, it fails with the messages:
mca_oob_tcp_accept: accept() failed with errno 9.
:
This didn't happen with 1.0.2.
The trigger for this behavior is if standard input happens to be clos
Brian Barrett wrote:
On Wed, 2006-06-28 at 09:43 -0400, Patrick Jessee wrote:
Hello. I've tracked down the source of the previously reported startup
problem with Openmpi 1.1. On startup, it fails with the messages:
mca_oob_tcp_accept: accept() failed with errno 9.
:
This d
Hello. I'm getting some odd error messages in certain situations
associated with the btl components (happens with both 1.0.2 and 1.1).
When certain btl components are NOT loaded, openMPI issues error
messages associated with those very components. For instance, consider
an application that
#x27;m a little confused about your response. Are you replying to the
"keyval parser" thread (i.e., saying that you had the same problem as
Benjamin Landsteiner), or are you replying to the "mca_oob_tcp_accept"
thread?
-Original Message-
From: users-boun...@open-mp
t are shipped in a
tarball hopefully do not suffer from such issues :-), and usually have
rpath information compiled in them so even LD_LIBRARY_PATH issues
shouldn't be much of a problem.
-Original Message-
From: users-boun...@open-mpi.org
[mailto:users-boun...@open-mpi.org] On B
Hello. I'm wondering if anyone knows of a way to get OpenMPI to compile
shared libraries without hard-coding the installation directory in
them. After compiling and installing OpenMPI, the shared libraries have
the installation libraries hard-coded in them. For instance:
$ ldd libmpi.so
e user installs it to /otherdir. I know
almost nothing about Fluent :-(, but do you wrap the call to mpirun
in a script/executable somewhere? Such that you could hide:
mpirun --prefix /otherdir ...
This might be good enough to do what you need.
Would that work?
On Nov 20, 200
10 matches
Mail list logo
