No, the session directory is created in the tmpdir - we don't create
anything anywhere else, nor do we write any executables anywhere.
Unfortunately, we don't have more debug statements internal to that
function. I'll have to create a patch for you that will add some so we can
better understand wh
I made sure the TMPDIR environment variable was set to /tmp for
non-interactive logins, and got the same result as before.
Also specifying the "-mca tmpdir_base /tmp" command-line options gave
the same result as well.
I made a mistake in my previous e-mail however -- the user home
directories ar
Open MPI needs to create a temporary directory structure that we call the
"session directory". This error is telling you that Open MPI was unable to
create that directory, probably due to a permission issue.
We decide on the root directory for the session directory using a
progression. You can dir
When I run with --debug-daemons, I get:
[node5.x86-64:09920] [0,0,1] ORTE_ERROR_LOG: Error in file
runtime/orte_init_stage1.c at line 626
--
It looks like orte_init failed for some reason; your parallel process
is
likely to
The correct options are --debug-daemons and --devel-debug
On 7/17/07 12:46 PM, "Bill Johnstone" wrote:
> George Bosilca wrote:
>
>> You can start by adding --debug-daemons and --debug to your mpirun
>> command line. This will generate a lot of output related to the
>> operations done internall
Sorry. The --debug was supposed to be --debug-devel. But I suspect
that if you have a normal build then there will be not much output.
However, --debug-daemons should give enough output so we can at least
have a starting point.
george.
On Jul 17, 2007, at 2:46 PM, Bill Johnstone wrote:
George Bosilca wrote:
> You can start by adding --debug-daemons and --debug to your mpirun
> command line. This will generate a lot of output related to the
> operations done internally by the launcher. If you send this output
> to the list we might be able to help you a little bit more.
OK, I ad
On 7/17/07, Bill Johnstone wrote:
> 2 - Check to make sure that all nodes have the openmpi installed
> and have the very same executable you are trying to run on the same
> path, have all permissions correctly.
Yes, they are all installed to /usr/local , the permissions are the
same, and if
On 7/17/07, Bill Johnstone wrote:
Thanks for the help. I've replied below.
--- "G.O." wrote:
> 1- Check to make sure that there are no firewalls blocking
> traffic between the nodes.
There is no firewall in-between the nodes. If I run jobs directly via
ssh, e.g. "ssh node4 env" they wo
Thanks for the help. I've replied below.
--- "G.O." wrote:
> 1- Check to make sure that there are no firewalls blocking
> traffic between the nodes.
There is no firewall in-between the nodes. If I run jobs directly via
ssh, e.g. "ssh node4 env" they work.
> 2 - Check to make sure tha
If you are having difficulty getting openmpi set up yourself, you
might look into OSCAR or Rocks, they make setting up your cluster much
easier and include various mpi packages as well as other utilities for
reducing your management overhead.
I can help you (off list) get set up with OSCAR if you
On 7/17/07, Bill Johnstone wrote:
Hello all.
I could really use help trying to figure out why mpirun is hanging as
detailed in my previous message yesterday, 16 July. Since there's been
no response, please allow me to give a short summary.
-Open MPI 1.2.3 on GNU/Linux, 2.6.21 kernel, gcc 4.1.
You can start by adding --debug-daemons and --debug to your mpirun
command line. This will generate a lot of output related to the
operations done internally by the launcher. If you send this output
to the list we might be able to help you a little bit more.
george.
On Jul 17, 2007, at 1
Hello all.
I could really use help trying to figure out why mpirun is hanging as
detailed in my previous message yesterday, 16 July. Since there's been
no response, please allow me to give a short summary.
-Open MPI 1.2.3 on GNU/Linux, 2.6.21 kernel, gcc 4.1.2, bash 3.2.15 is
default shell
-Open
On Tue, Jul 17, 2007 at 07:17:58AM -0400, Jeff Squyres wrote:
> Unfortunately, this looks like a problem with your gcc installation
> -- a compiler should never seg fault when it's trying to compile C
> source code.
>
> FWIW: the file in question that it's trying to compile is actually
> fro
Unfortunately, this looks like a problem with your gcc installation
-- a compiler should never seg fault when it's trying to compile C
source code.
FWIW: the file in question that it's trying to compile is actually
from GNU Libtool (which is included in Open MPI).
You should probably inve
Hello,
When i try to install OpenMPI on Linux Suse 10.2 on AMDX2 Dual Core
processor i get the following message:
make[3]: Entering directory `/home/igor/openmpi-1.2.3/opal/libltdl'
if /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I. -D
LT_CONFIG_H='' -DLTDL -I. -I. -Il
17 matches
Mail list logo
