Apologies, I have not taken the time to read your comprehensive diagnostics!
As Gus says, this sounds like a memory problem.
My suspicion would be the kernel Out Of Memory (OOM) killer.
Log into those nodes (or ask your systems manager to do this). Look
closely at /var/log/messages where there wil
Hi, Gus and John,
my code (zeusmp2) is a F77 code ported in F95, and the very first time
I have launched it, the processed disappears almost immediately.
I checked the code with valgrind and some unallocated arrays were
passed wrongly to some subroutines.
After having corrected this bug, the code
Hi,
I have one more question.
I wanted to experiment with processor affinity command-line options on my
ubuntu PC.
When I use OpenMPI compiled from sourecs a few weeks ago, mpirun returns
error messages.
However, the"official" OpenMPI installation on the same machine makes no
problem.
Does it mean
You are using cmd line options that no longer exist in the 1.9 release - look
at "mpirun -h" for the current list of options.
FWIW: in your example, the correct cmd line would be:
mpirun -np 2 --bind-to core -map-by core --report-bindings uptime
Note the space in "--bind-to core" and the "-map-
Thanks, Ralph,
the new syntax works well (I used "man mpirun", which displayed the old
syntax).
Also, the report displayed by --report-binding is far more human-readable
than in previous versions of OpenMPI
Out of curiosity, and also to supress the warning, I installed the
libnuma-dev package wit
I have tried to run with a single process (i.e. the entire grid is
contained by one process) and the the command free -m on the compute
node returns
total used free sharedbuffers cached
Mem: 3913 1540 2372 0 49 1234
-
On Sep 1, 2012, at 4:33 AM, Zbigniew Koza wrote:
> Thanks, Ralph,
>
> the new syntax works well (I used "man mpirun", which displayed the old
> syntax).
Ouch - will have to fix that. Thx
> Also, the report displayed by --report-binding is far more human-readable
> than in previous versions
All,
I am quite new to using Open MPI as it is required by programs that I
use for research. While running a chemistry program through Terminal, I
inadvertently hit enter after I tried to run the program over multiple
processors and am now getting one of two errors when I try and run th
The root cause is that you didn't specify an executable to run.
However, we might have some help messages missing, too. What version of OMPI
are you running?
Sent from my phone. No type good.
On Sep 1, 2012, at 12:22 PM, "Austin Baker"
mailto:as...@pitt.edu>> wrote:
All,
I am quite new to us
I have the most current version installed. I tried that first.
Austin Baker
as...@pitt.edu
Graduate Student
Department of Chemistry
University of Pittsburgh
Everything is Experimental
On Sep 1, 2012, at 12:41 PM, Jeff Squyres (jsquyres) wrote:
> The root cause is that you didn't specify an exe
Current meaning 1.6.1, 1.9, 1.7,???
A simple "ompi_info" will tell you at the very top:
Package: Open MPI rhc@Ralphs-iMac.local Distribution
Open MPI: 1.9a1r27207M
On Sep 1, 2012, at 10:10 AM, Austin Baker wrote:
> I have the most current version installed
Am 01.09.2012 um 18:20 schrieb Austin Baker:
> All,
>
> I am quite new to using Open MPI as it is required by programs that I
> use for research. While running a chemistry program through Terminal, I
> inadvertently hit enter after I tried to run the program over multiple
> processors an
12 matches
Mail list logo
