For the mailing list: the issue is that some M1's apparently default to an
unlimited max number of open files per process. If you use "ulimit -n" to set
some reasonable number, then Open MPI should behave better:
ulimit -n 1024
mpirun ...
We don't (yet?) know why this seems to be necessary on
Scott and I conversed a bit off list, and I got more data. I posted everything
in https://github.com/open-mpi/ompi/issues/10358 -- let's follow up on this
issue there.
--
Jeff Squyres
jsquy...@cisco.com
From: George Bosilca
Sent: Thursday, May 5, 2022
That is weird, but maybe it is not a deadlock, but a very slow progress. In
the child can you print the fdmax and i in the frame do_child.
George.
On Thu, May 5, 2022 at 11:50 AM Scott Sayres via users <
users@lists.open-mpi.org> wrote:
> Jeff, thanks.
> from 1:
>
> (lldb) process attach --pid 9
Jeff, thanks.
from 1:
(lldb) process attach --pid 95083
Process 95083 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
frame #0: 0x0001bde25628 libsystem_kernel.dylib`close + 8
libsystem_kernel.dylib`close:
-> 0x1bde25628 <+8>: b.lo 0x1bde25648
You can use "lldb -p PID" to attach to a running process.
--
Jeff Squyres
jsquy...@cisco.com
From: Scott Sayres
Sent: Thursday, May 5, 2022 11:22 AM
To: Jeff Squyres (jsquyres)
Cc: Open MPI Users
Subject: Re: [OMPI users] mpirun hangs on m1 mac w openmpi-
Jeff,
It does launch two mpirun processes (when hung from another terminal window)
scottsayres 95083 99.0 0.0 408918416 1472 s002 R 8:20AM
0:04.48 mpirun -np 4 foo.sh
scottsayres 95085 0.0 0.0 408628368 1632 s006 S+8:20AM
0:00.00 egrep mpirun|foo.sh
scottsayres
Any chance this is all due to an OS X security setting? Apple has
been putting locked doors on many, many things lately.
On Thu, May 5, 2022 at 8:57 AM Jeff Squyres (jsquyres) via users
wrote:
>
> Scott --
>
> Sorry; something I should have clarified in my original email: I meant you to
> run
Scott --
Sorry; something I should have clarified in my original email: I meant you to
run the "ps" command **while mpirun was still hung**. I.e., do it in another
terminal, before you hit ctrl-C to exit mpirun.
I want to see if mpirun has launched the foo.sh or not. Gilles' test is a
differ
Scott,
I am afraid this test is inconclusive since stdout is processed by mpirun.
What if you
mpirun -np 1 touch /tmp/xyz
abort (since it will likely hang) and
ls -l /tmp/xyz
In my experience on mac, this kind of hangs can happen if you are running a
firewall and/or the IP of your host does not
