Hello Jeff, In short, Yes.
To further explain what I meant, I see many problems which will just end in termination of the MPI job, sharing the same error message (which is just saying that the process aborted) while the underlying reason are different, sometimes related to the code, some other times related to hardware, networking, configuration of Infiniband. I want when I get such error to have details that guide me to which area I should investigate, without spitting very detailed logs like the output of strace for example, so it doesn't make the actual output of the MPI job harder to read. I assume it could be either something enabled during compilation of OMPI itself, or something passed during runtime (will be better). All the best, -- Passant ________________________________________ From: Jeff Squyres (jsquyres) <jsquy...@cisco.com> Sent: Sunday, July 28, 2019 5:52 PM To: Open MPI User's List Cc: Passant A. Hafez Subject: Re: [OMPI users] Debug OMPI errors I'm not sure exactly what you are asking -- can you be more specific? Are you asking if Open MPI can emit more detail when an error occurs and the job aborts? > On Jul 28, 2019, at 4:12 AM, Passant A. Hafez via users > <users@lists.open-mpi.org> wrote: > > Hello all, > > I was wondering if I can enable some reasonable level of debugging for OMPI > errors, especially in the cases that just report that a process is killed > (for example MPI_ABORT was invoked) and that's it. > > > > All the best, > > -- > > Passant > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users -- Jeff Squyres jsquy...@cisco.com _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
