foo.sh is executable, again hangs without output.
I command c x2 to return to shell, then
ps auxwww | egrep 'mpirun|foo.sh'
output shown below
scottsayres@scotts-mbp trouble-shoot % ./foo.sh
Wed May 4 12:59:15 MST 2022
Wed May 4 12:59:16 MST 2022
Wed May 4 12:59:17 MST 2022
Wed May 4 12:5
That backtrace seems to imply that the launch may not have completed.
Can you make an executable script foo.sh with:
#!/bin/bash
i=0
while test $i -lt 10; do
date
sleep 1
let i=$i+1
done
Make sure that foo.sh is executable and then run it via:
mpirun -np 1 foo.sh
If you sta
Following Jeff's advice, I have rebuilt open-mpi by hand using the -g
option. This shows more information as below. I am attempting George's
advice of how to track the child but notice that gdb does not support
arm64. attempting to update lldb.
scottsayres@scotts-mbp openmpi-4.1.3 % lldb mpir
George beat me to the reply. :-)
His advice is the correct one (check out what's happening in a debugger). This
will likely work better with a hand-built Open MPI (vs. Homebrew), because then
you can configure/build Open MPI with -g so that the debugger will be able to
see the source code. E
Scott,
This shows the deadlock arrives during the local spawn. Here is how things
are supposed to work: the mpirun process (parent) will fork (the child),
and these 2 processes are connected through a pipe. The child will then
execve the desired command (hostname in your case), and this will close
Hi George, Thanks! You have just taught me a new trick. Although I do not
yet understand the output, it is below:
scottsayres@scotts-mbp ~ % lldb mpirun -- -np 1 hostname
(lldb) target create "mpirun"
Current executable set to 'mpirun' (arm64).
(lldb) settings set -- target.run-args "-np" "1
I compiled a fresh copy of the 4.1.3 branch on my M1 laptop, and I can run
both MPI and non-MPI apps without any issues.
Try running `lldb mpirun -- -np 1 hostname` and once it deadlocks, do a
CTRL+C to get back on the debugger and then `backtrace` to see where it is
waiting.
George.
On Wed, Ma
Thanks for looking at this Jeff.
No, I cannot use mpirun to launch a non-MPI application.The command
"mpirun -np 2 hostname" also hangs.
I get the following output if I add the -d command before (I've replaced
the server with the hashtags) :
[scotts-mbp.3500.dhcp.###:05469] procdir:
/var/fol
Are you able to use mpirun to launch a non-MPI application? E.g.:
mpirun -np 2 hostname
And if that works, can you run the simple example MPI apps in the "examples"
directory of the MPI source tarball (the "hello world" and "ring" programs)?
E.g.:
cd examples
make
mpirun -np 4 hello_c
mpirun
