You should probably also run the ompi_info command; it tells you details about
your installation, and how it was configured.
Is it known that OpenFoam uses threads with MPI?
On Jan 17, 2012, at 9:08 AM, Ralph Castain wrote:
> You might first just try running a simple MPI "hello" to verify the
Not even the subway, but the bus:-)
Currently just building the application on my laptop for prototyping. Will
eventually move to a win-only commodity boxes in 1 lan, or RHEL boxes in the
long term,
Unfortunately not possible to mix both.
The ideal solution would be some hybrid of openmp + openmpi
I have not tried to support a MTL with the checkpointing functionality, so
I do not have first hand experience with those - just the OB1/BML/BTL stack.
The difficulty in porting to a new transport is really a function of how
the transport interacts with the checkpointer (e.g., BLCR). The draining
But that would be yet another legitimate singleton-edge-case that OpenMPI could
proudly handle, wouldn't it?
No network connection, yet OpenMPI is still operational in a standalone insular
machine.
IMHO, MM made a good case for his 'commuter MPI'. :)
Times change, I would never have thought that
I think it won't help - it looks like mpirun itself aborts if it only finds
a loopback available.
On Tue, Jan 17, 2012 at 9:24 AM, Gustavo Correa wrote:
> MM
> Have you tried adding '-mca btl sm,self' to your mpirun command line,
> as suggested by Terry? [despite the low chances that it would wor
MM
Have you tried adding '-mca btl sm,self' to your mpirun command line,
as suggested by Terry? [despite the low chances that it would work ...]
If somehow the loopback interface is up, wouldn't it work?
Gus Correa
On Jan 17, 2012, at 7:01 AM, MM wrote:
> Gus, unfortunately, it doesn't seem to ch
I'll look - can probably add something to fall back to localhost if nothing
else is available
On Tue, Jan 17, 2012 at 8:02 AM, MM wrote:
> Even with a -host localhost ? Is there a way to change that?
>
> I have a long commute from work and I run 4 mpi processes on my quadcore
> laptop, and
Yes this is what I'd need exactly. That sounds great to just include in the
released binaries then.
I believe most people who download the binaries will use them to link
against those mpi libraries and therefore they write source code, so they
debug it.
The user can built release, and would need
slurm 2.3.2
-Andrew
On Tue, Jan 17, 2012 at 6:05 PM, Ralph Castain wrote:
> What version of slurm?
>
>
> Sent from my iPad
>
> On Jan 17, 2012, at 4:36 AM, Andrew Senin wrote:
>
>> Hi Ralph,
>>
>> If you want Mike can provide access to the lab with RHEL 6.0 where we
>> see the problem.
>>
>> Th
Hi MM,
Actually option 3 has already been implemented for Windows build, and it
seems adequate. But it was not targeting for the windows binary, as only
quite a few users require this feature.
When enabling WANT_EXE_DEBUG_POSTFIX option in CMake GUI, the build
system will generate mpic++.exe
Even with a -host localhost ? Is there a way to change that?
I have a long commute from work and I run 4 mpi processes on my quadcore
laptop, and while commuting, there's no connection:-)
MM
From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] On
Behalf Of Ralph Castain
Sent:
I believe it is looking for a non-loopback interface.
Sent from my iPad
On Jan 17, 2012, at 5:01 AM, "MM" wrote:
> Gus, unfortunately, it doesn't seem to change the error.
> Ralph, with the wireless adapter disabled, netstat on winxp still shows
> these ports as listening:
> Shouldn't the MS
You might first just try running a simple MPI "hello" to verify the
installation. I don't know if OF is threaded or not.
Sent from my iPad
On Jan 17, 2012, at 5:22 AM, John Hearns wrote:
> Andre,
> you should not need the OpenMPI sources.
>
> Install the openmpi-devel package from the same so
What version of slurm?
Sent from my iPad
On Jan 17, 2012, at 4:36 AM, Andrew Senin wrote:
> Hi Ralph,
>
> If you want Mike can provide access to the lab with RHEL 6.0 where we
> see the problem.
>
> Thanks,
> Andrew Senin
>
> On Tue, Jan 17, 2012 at 9:59 AM, Mike Dubman wrote:
>> It happen
Andre,
you should not need the OpenMPI sources.
Install the openmpi-devel package from the same source
(zypper install openmpi-devel if you have that science repository enabled)
This will give you the mpi.h file and other include files, libraries
and manual pages.
That is a convention in Suse-sty
Gus, unfortunately, it doesn't seem to change the error.
Ralph, with the wireless adapter disabled, netstat on winxp still shows
these ports as listening:
Shouldn't the MS TCP Loopback interface allow the tcp ports to be created?
>netstat -an
Active Connections
Proto Local Address
Hi Ralph,
If you want Mike can provide access to the lab with RHEL 6.0 where we
see the problem.
Thanks,
Andrew Senin
On Tue, Jan 17, 2012 at 9:59 AM, Mike Dubman wrote:
> It happens for us on RHEL 6.0
>
>
> On Tue, Jan 17, 2012 at 3:46 AM, Ralph Castain
> wrote:
>>
>> Well, I'm afraid I can't
Is there a way to set up an interface analogous to Unix's loopback? I
suspect setting "-mca btl self,sm" wouldn't help since this is probably
happening while the processes are bootstrapping.
--td
On 1/16/2012 7:26 PM, Ralph Castain wrote:
The problem is that OMPI is looking for a tcp port fo
Hi Devendra,
thanks for your interesting answer, up to now I expected to get a fully
operational openmpi installation package
by installing openmpi from the “science” repository (
http://download.opensuse.org/repositories/science/openSUSE_11.3” ).
To compile your script I need to have the openmpi
It happens for us on RHEL 6.0
On Tue, Jan 17, 2012 at 3:46 AM, Ralph Castain wrote:
> Well, I'm afraid I can't replicate your report. It runs fine for me.
>
> Sent from my iPad
>
> On Jan 16, 2012, at 4:25 PM, Ralph Castain wrote:
>
> > Hprobably a bug. I haven't tested that branch yet.
20 matches
Mail list logo
