Open MPI should likely write this message on stderr, I will have a look
at that.
That being said, and though I have no intention to dodge the question,
this case should not happen.
A well written (MPI) program should either exit(0) or have main() return
0, so this scenario
(e.g. all MPI tasks call MPI_Finalize() and then at least one MPI task
exit with a non zero error code)
should not happen.
If your program might fail, it should call MPI_Abort() with a non zero
error code *before* calling MPI_Finalize().
note this error can occur if your main() subroutine does not return any
value (e.g. it returns an undefined value, that might be non zero)
Cheers,
Gilles
On 9/5/2018 6:08 AM, emre brookes wrote:
Background:
---
Running on ubuntu 16.04 with apt install openmpi-bin libopenmpi-dev
$ mpirun --version
mpirun (Open MPI) 1.10.2
I did search thru the docs a bit (ok, maybe I missed something
obvious, my apologies if so)
---
Question:
Is there some setting to turn off the extra messages generated by
openmpi ?
e.g.
$ mpirun -np 2 my_job > my_job.stdout
adds this message to my_job.stdout
-------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code.. Per user-direction, the job has been aborted.
-------------------------------------------------------
which strangely goes to stdout and not stderr.
I would intuitively expect error or notice messages to go to stderr.
Is there a way to redirect these messages to stderr or some specified
file?
I need to separate this from the collected stdout of the job processes
themselves.
Somewhat kludgy options that come to mind:
1. I can use --output-filename outfile, which does separate the
"openmpi" messages,
but this creates a file for each process and I'd rather keep them as
produced in one file,
but without any messages from openmpi, which I'd like to keep separately.
2. Or I could write a script to filter the output and separate. A bit
risky as someone could conceivably put something that looks like a
openmpi message pattern in the mpi executable output.
3. hack the source code of openmpi.
Any suggestions as to a more elegant or standard way of dealing with
this?
TIA,
Emre.
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
