Thanks for all the suggestions. I'm able to get it to work now using the
simpler config line suggested. I did not fully explain my setup but it
turns out due to a mount error my machine was not seeing the new files in
the rebuilt openmpi directory which was remotely mounted, so I kept getting
the s
--Original Message--
From: Gustavo Correa
Sender: users-boun...@open-mpi.org
To: Open MPI Users
ReplyTo: Open MPI Users
Sent: Dec 7, 2011 1:10 PM
Subject: Re: [OMPI users] orte_ess_base_select failed
Hi John Doe
I would keep it very simple, particularly if you are just starting with MPI
On Dec 7, 2011, at 10:45 AM, John Doe wrote:
> Ok. That did help a bit. I now see that the /opt/ompi/gnu/1.4.4/lib/openmpi/
> directory has .so files as well as the .la files. Unfortunately I still get
> the same error when I run i.e it complains about missing files in that
> directory even t
Did you do a 'make distclean' before you started anew?
On Dec 7, 2011, at 12:45 PM, John Doe wrote:
> Ok. That did help a bit. I now see that the /opt/ompi/gnu/1.4.4/lib/openmpi/
> directory has .so files as well as the .la files. Unfortunately I still get
> the same error when I run i.e it com
Hi John Doe
Set these environment variables in your .profile/.bashrc or .[t]cshrc file.
If you set them in the shell prompt, before you run the job, I am not sure they
will
propagate to the MPI processes, even if you are running in a standalone machine
[which apparently you are].
Ralph may clari
Hi John Doe
I would keep it very simple, particularly if you are just starting with MPI or
OpenMPI.
Why not this?
./configure --prefix=/opt/ompi/gnu/1.4.4
You may also point to the compilers CC, CXX, F77. FC, for C, C++, Fortran-77
and Fortran-90,
respectively , in case they are not in stand
Ok. That did help a bit. I now see that the
/opt/ompi/gnu/1.4.4/lib/openmpi/ directory has .so files as well as the .la
files. Unfortunately I still get the same error when I run i.e it complains
about missing files in that directory even though those files are present
with an .so or .la extension
Hi Ralph,
I may have been a little promiscous in my use of build flags. My initial
configure line was much simpler then I kept throwing in flags when it
wouldn't run. I'll try to build it again with the your config line and see
if that resolves the issue.
Sam
On Wed, Dec 7, 2011 at 11:11 AM, Ra
I don't understand your configure line - why did you give an argument to
enable-shared?? That option doesn't take an argument, and may be causing the
confusion. Also, enable-debug by default turns off optimization as otherwise
the optimizer removes all debug symbols.
If you want a debug version
Hi Gustavo,
I do have /opt/ompi/gnu/1.4.4/lib in my LD_LIBRARY_PATH and the bin
directory in my path as well but that didn't seem to help.
Sam
On Tue, Dec 6, 2011 at 5:18 PM, Gustavo Correa wrote:
> Hi John Doe
>
> What you need to add to LD_LIBRARY_PATH is /opt/ompi/gnu/1.4.4/lib
> [note 'lib
Hi John Doe
What you need to add to LD_LIBRARY_PATH is /opt/ompi/gnu/1.4.4/lib
[note 'lib' at the end].
Your email seems to say that you added /opt/ompi/gnu/1.4.4/lib/openmpi
instead, if I understood it right.
And to your PATH you need to add the corresponding 'bin' directory:
/opt/ompi/gnu/1.4.4
Jeff Squyres wrote:
Run with "--mca ess_base_verbose 1000" on the mpirun command line and
send the output, such as:
mpirun --mca ess_base_verbose 1000 rest of your command here...
On Mar 30, 2009, at 5:33 PM, Russell McQueeney wrote:
I only invoked orted manually to see the error mess
Run with "--mca ess_base_verbose 1000" on the mpirun command line and
send the output, such as:
mpirun --mca ess_base_verbose 1000 rest of your command here...
On Mar 30, 2009, at 5:33 PM, Russell McQueeney wrote:
I only invoked orted manually to see the error message, as it wasn't
sh
I only invoked orted manually to see the error message, as it wasn't
showing up on the node's monitor or the xterm window i used to run
mpirun. And no, no prefix command, no aliases, no absolute path,
environment variables set.
You should not be invoking orted manually -- getting errors when you
invoke orted manually is probably to be expected.
Can you answer the questions from my original mail? Thanks.
On Mar 27, 2009, at 6:29 PM, Russell McQueeney wrote:
Jeff Squyres wrote:
> Hmm -- puzzling -- the error file y
Jeff Squyres wrote:
Hmm -- puzzling -- the error file you sent shows the following:
bash: /opt/openmpi/orted: No such file or directory
But that shouldn't happen; according to your config.log, you installed
with a prefix of /opt/openmpi, so Open MPI should be looking for orted
in /opt/openmpi
Hmm -- puzzling -- the error file you sent shows the following:
bash: /opt/openmpi/orted: No such file or directory
But that shouldn't happen; according to your config.log, you installed
with a prefix of /opt/openmpi, so Open MPI should be looking for orted
in /opt/openmpi/bin/orted.
You s
command = mpirun --hostfile hostfile -np 2 echo `uname -a`
PATH = ...:/opt/openmpi/bin
LD_LIBRARY_PATH = /opt/openmpi/lib
no MCA parameters used
I set up the default shell to bash, and put some echo's in .bash_profile
and .bashrc, and when i run the mpirun command, i see those echoes, but
then
Could you please send the info shown here:
http://www.open-mpi.org/community/help/
If the ess is failing, then we don't recognize the environment.
Probably an issue with how it is configured vs being run.
Thanks
Ralph
On Mar 26, 2009, at 3:42 PM, Russell McQueeney wrote:
I installed OpenMP
19 matches
Mail list logo
