If it would have been a problem with nohup and openmpi would the problem be
always reproducible.
But this problem is occuring intermittently only.
Some jobs even get completed without any problem.
While your method starts mpirun itself nohup, the mpi processes themselves are
not launched that way and therefore run in the foreground. This message
indicates that at least one of those mpi processes received a hangup signal and
aborted. Even though mpirun won't get the signal itself, it does
Thank you very much. That was it. I didn't know that by default it was any
firewall running on the default Yellow Dog Linux installations since nothing
was asked about this issue during the installation.
You really saved my day George.
Regards,
Chris
On Wed, Sep 17, 2008 at 2:24 PM, George Bosilc
Christophe,
Looks like a firewall problem. Please check the mailing list archives
for the proper fix.
Thanks,
george.
On Sep 17, 2008, at 6:53 AM, Christophe Spaggiari wrote:
Hi,
I am new to MPI and try to get my Open MPI environment up and
running. I have two machines Alpha and B
