- Forwarded Message -
From: Hamilton Fischer
To: "u...@open-mpi.org"
Sent: Monday, January 16, 2012 9:09 PM
Subject: unknown af_family recieved errors...
Hi, I'm having odd issues with my "cluster", I guess. This very simple example
works on one machine, but it gives a load of err
After some searching, it turns out mpi4py tries to call MPI_Init_thread but
python in general has issues with threads apparently. I'm backing off from
threading at this point.
noobermin
From: TERRY DONTJE
To: us...@open-mpi.org
Sent: Wednesday, January 11,
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. Will take a look.
>
> Sent from my iPad
>
> On Jan 16, 2012, at 11:56 AM, Andrew Senin wrote:
The problem is that OMPI is looking for a tcp port for your computer. With no
network enabled, you don't have one, and so mpirun aborts. I don't know of any
way around this at the moment.
Sent from my iPad
On Jan 16, 2012, at 4:53 PM, Gustavo Correa wrote:
> Have you tried to specify the host
Have you tried to specify the hosts with something like this?
mpirun -np 2 -host localhost ./my_program
See 'man mpirun' for more details.
I hope it helps,
Gus Correa
On Jan 16, 2012, at 6:34 PM, MM wrote:
> hi,
>
> when my wireless adapter is down on my laptop, only localhost is configured.
hi,
when my wireless adapter is down on my laptop, only localhost is configured.
In this case, when I mpirun 2 binaries on my laptop, mpirun fails with this
error:
It looks like orte_init failed for some reason; your parallel process i
likely to abort. There are many reasons that a paral
Hprobably a bug. I haven't tested that branch yet. Will take a look.
Sent from my iPad
On Jan 16, 2012, at 11:56 AM, Andrew Senin wrote:
> Hi,
>
> I think I've found a bug in the hear revision of the OpenMPI 1.5
> branch. If it is configured with --disable-debug it crashes in
> finaliz
Hi,
I think I've found a bug in the hear revision of the OpenMPI 1.5
branch. If it is configured with --disable-debug it crashes in
finalize on the hello_c.c example. Did I miss something out?
Configure options:
./configure --with-pmi=/usr/ --with-slurm=/usr/ --without-psm
--disable-debug --enabl
Hello,
It would be useful for the end user to use mpic++ to obtain the compile and
link flags for both release and debug builds.
There is a number of possible solutions:
1. add the showme flags of mpic++ and any other similar binary to
something like -showme:compile_debug -showme:compi
Hello Andre,
It may be possible that your openmpi does not support threaded MPI-calls (if
these are happening). I had a similar problem, and it was traced to this cause.
If you installed your openmpi from available repositories, chances are that you
do not have thread-support.
Here's a small s
Hi everyone,
may I have your help on a strange problem?
High performance computing is new to me and I have not much idea about OpenMPI
and OpenFoam (OF) which uses the "mpirun" command.
I have to support the OF application in my company and have been trying to find
the problem since about 1 week
11 matches
Mail list logo
