To add more info, here is a backtrace of the spawned (hung) program.
(gdb) bt
#0 0xe410 in __kernel_vsyscall ()
#1 0x402cdaec in sched_yield () from /lib/tls/libc.so.6
#2 0x4016360c in opal_progress () at runtime/opal_progress.c:301
#3 0x403a9b29 in mca_oob_tcp_msg_wait (msg=0x805cc70,
Hi Edgar,
I changed the spawned program from /bin/hostname to a very simple MPI
program as below. But now, the slave hangs right at MPI_Init line.
What could the issue be?
slave.c
#include
#include
#include
#include "mpi.h"
#include /* standard system types */
#include
MPI_Comm_spawn is tested nightly by the test our suites, so it should
definitely work...
Thanks
Edgar
Prakash Velayutham wrote:
Thanks Edgar. I did not know that. Really?
Anyways, you are sure, an MPI job will work as a spawned process
instead of "hostname"?
Thanks,
Prakash
On Dec 1,
Thanks Edgar. I did not know that. Really?
Anyways, you are sure, an MPI job will work as a spawned process
instead of "hostname"?
Thanks,
Prakash
On Dec 1, 2007, at 5:56 PM, Edgar Gabriel wrote:
MPI_Comm_spawn has to build an intercommunicator with the child
process
that it spawns.
MPI_Comm_spawn has to build an intercommunicator with the child process
that it spawns. Thus, you can not spawn a non-MPI job such as
/bin/hostname, since the parent process waits for some messages from the
child process(es) in order to set up the intercommunicator.
Thanks
Edgar
Prakash
