Re: [OMPI users] MPI_ABORT, indirect execution of executables by mpirun, Open MPI 2.1.1

Ted, note that the shell receives a SIGTERM followed by a SIGKILL (if needed ?) from Open MPI so if you cannot exec the MPI binary, you have the option to trap SIGTERM in your shell script, and then manually propagate it (or a SIGKILL) to the MPI app Cheers, Gilles On Fri, Jun 16, 2017 at 6:44

Re: [OMPI users] MPI_ABORT, indirect execution of executables by mpirun, Open MPI 2.1.1

You have to understand that we have no way of knowing who is making MPI calls - all we see is the proc that we started, and we know someone of that rank is running (but we have no way of knowing which of the procs you sub-spawned it is). So the behavior you are seeking only occurred in some ear

Re: [OMPI users] MPI_ABORT, indirect execution of executables by mpirun, Open MPI 2.1.1

Hello Ralph, I am just an Open MPI end user, so I will need to wait for the next official release. mpirun --> shell for process 0 --> executable for process 0 --> MPI calls --> shell for process 1 --> executable for process 1 --> MPI calls ... I guess the

Re: [OMPI users] MPI_ABORT, indirect execution of executables by mpirun, Open MPI 2.1.1

Yeah, things jittered a little there as we debated the “right” behavior. Generally, when we see that happening it means that a param is required, but somehow we never reached that point. See if https://github.com/open-mpi/ompi/pull/3704 helps - if so

Re: [OMPI users] MPI_ABORT, indirect execution of executables by mpirun, Open MPI 2.1.1

Thank you for your comments. Our application relies upon "dum.sh" to clean up after the process exits, either if the process exits normally, or if the process exits abnormally because of MPI_ABORT. If the process group is killed by MPI_ABORT, this clean up will not be performed. If exec is

Re: [OMPI users] MPI_ABORT, indirect execution of executables by mpirun, Open MPI 2.1.1

Here is how the system is working: Master: each process is put into its own process group upon launch. When we issue a “kill”, however, we only issue it to the individual process (instead of the process group that is headed by that child process). This is probably a bug as I don’t believe that

Re: [OMPI users] MPI_ABORT, indirect execution of executables by mpirun, Open MPI 2.1.1

Hello Gilles, Thank you for your quick answer. I confirm that if exec is used, both processes immediately abort. Now suppose that the line echo "After aborttest: OMPI_COMM_WORLD_RANK="$OMPI_COMM_WORLD_RANK is added to the end of dum.sh. If Example 2 is run with Open MPI 1.4.3, the output is

Re: [OMPI users] Double free or corruption with OpenMPI 2.0

Hello Jeff and Gilles, I just logged in to see the archives and this message of Gilles - https://www.mail-archive.com/users@lists.open-mpi.org//msg31219.html and this message of Jeff - https://www.mail-archive.com/users@lists.open-mpi.org//msg31217.html are very use