Later I change another machine and set the TMPDIR to default /tmp, but the
problem (low CPU utilization under 20%) still occur :<
Vincent
On Thu, Oct 23, 2014 at 10:38 PM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> If normal users can't write to /tmp (or if /tmp is an NFS-mounted
> f
How can I fix the error if all processes open their backing files for mmap
on NSF like you said?
Vincent
On Thu, Oct 23, 2014 at 10:35 PM, Joshua Ladd wrote:
> It's not coming from OSHMEM but from the OPAL "shmem" framework. You are
> going to get terrible performance - possibly slowing to a cr
Hi Siegmar,
The attached JRE log shows very important information.
When JRE loads the MPI class, JNI_OnLoad function in
libmpi_java.so (Open MPI library; written in C) is called.
And probably mca_base_var_cache_files function passes NULL
to asprintf function. I don't know how this situation occur
Hello Siegmar,
If your Java program only calls to MPI.Init and MPI.Finalize you don't
need debug Java. The JNI layer is very thin, so I think the problem is
not in Java. Also, if the process crash is in the JNI side, debugging
won't provides you useful information.
But if you want debug 2 pr
Hello Oscar,
do you have time to look into my problem? Probably Takahiro has a
point and gdb behaves differently on Solaris and Linux, so that
the differing outputs have no meaning. I tried to debug my Java
program, but without success so far, because I wasn't able to get
into the Java program to
If normal users can't write to /tmp (or if /tmp is an NFS-mounted filesystem),
that's the underlying problem.
@Vinson -- you should probably try to get that fixed.
On Oct 23, 2014, at 10:35 AM, Joshua Ladd wrote:
> It's not coming from OSHMEM but from the OPAL "shmem" framework. You are
> g
It's not coming from OSHMEM but from the OPAL "shmem" framework. You are
going to get terrible performance - possibly slowing to a crawl having all
processes open their backing files for mmap on NSF. I think that's the
error that he's getting.
Josh
On Thu, Oct 23, 2014 at 6:06 AM, Vinson Leung
Hi Siegmar,
> I think that it must have to do with MPI, because everything
> works fine on Linux and my Java program works fine with an older
> MPI version (openmpi-1.8.2a1r31804) as well.
Yes. I also think it must have to do with MPI.
But java process side, not mpiexec process side.
When you ru
HI, Thanks for your reply:)
I really run an MPI program (compile with OpenMPI and run with "mpirun -n 8
.."). My OpenMPI version is 1.8.3 and my program is Gromacs. BTW, what
is OSHMEM ?
Best
Vincent
On Thu, Oct 23, 2014 at 12:21 PM, Ralph Castain wrote:
> From your error message, I gather
> "Bill" == Bill Broadley writes:
Hi Bill,
>> I've commented in detail on this (non-)issue on 2014-08-20:
>> http://www.open-mpi.org/community/lists/users/2014/08/25090.php
Bill> I read that. It seems pretty clear what the problem is, but
Bill> not so clear on what a user
From your error message, I gather you are not running an MPI program, but
rather an OSHMEM one? Otherwise, I find the message strange as it only would be
emitted from an OSHMEM program.
What version of OMPI are you trying to use?
> On Oct 22, 2014, at 7:12 PM, Vinson Leung wrote:
>
> Thanks f
11 matches
Mail list logo
