[petsc-dev] [mpich-discuss] turning off MPI abort messages

William Gropp wgropp at illinois.edu
Fri Feb 21 17:08:22 CST 2014


My thanks too.  My position, as Barry notes, is that if you ever use | (pipe) in a shell command, you agree with me, even if you don't know it :).  One of the fundamental strengths of Unix is the easy ability to build tools by composing other tools with pipe, and programs and systems that insist on gratuitous output break this model; they become second class citizens in the Unix world.  

Bill

William Gropp
Director, Parallel Computing Institute
Deputy Director for Research
Institute for Advanced Computing Applications and Technologies
Thomas M. Siebel Chair in Computer Science
University of Illinois Urbana-Champaign




On Feb 21, 2014, at 2:32 PM, Barry Smith wrote:

> 
>   Jeff,
> 
>     Thanks. This is certainly a useful thing. 
> 
>      I never meant to kick a hornet’s nest with my initial email. I was taught by my postdoctoral advisor that any library or package that had stdout or stderr output hardwired that could not be turned off without losing functionality was rude and poorly thought out but then that guy probably never amounted to anything I guess so I should just ignore him since he doesn’t represent main stream thought.
> 
>   Barry
> 
> On Feb 21, 2014, at 3:10 PM, Jeff Hammond <jeff.science at gmail.com> wrote:
> 
>> Barry:
>> 
>> Would the following behavior be acceptable to you?  I have only made
>> the changes in MPI but am looking at the process manager now.
>> 
>> Jeff
>> 
>> 
>> # Without the process manager
>> 
>> alcfwl181:build jhammond$ export MPIR_CVAR_SUPPRESS_ABORT_MESSAGE=0
>> alcfwl181:build jhammond$ ./a.out
>> application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
>> alcfwl181:build jhammond$ export MPIR_CVAR_SUPPRESS_ABORT_MESSAGE=1
>> alcfwl181:build jhammond$ ./a.out
>> 
>> alcfwl181:build jhammond$ unset MPIR_CVAR_SUPPRESS_ABORT_MESSAGE
>> alcfwl181:build jhammond$ ./a.out
>> application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
>> 
>> # With the process manager
>> 
>> alcfwl181:build jhammond$ mpiexec -n 1 -env
>> MPIR_CVAR_SUPPRESS_ABORT_MESSAGE 0 ./a.out
>> application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
>> 
>> ===================================================================================
>> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
>> =   PID 61023 RUNNING AT alcfwl181.alcf.anl.gov
>> =   EXIT CODE: 1
>> =   CLEANING UP REMAINING PROCESSES
>> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>> ===================================================================================
>> alcfwl181:build jhammond$ mpiexec -n 1 -env
>> MPIR_CVAR_SUPPRESS_ABORT_MESSAGE 1 ./a.out
>> 
>> 
>> ===================================================================================
>> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
>> =   PID 61026 RUNNING AT alcfwl181.alcf.anl.gov
>> =   EXIT CODE: 1
>> =   CLEANING UP REMAINING PROCESSES
>> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>> ===================================================================================
>> alcfwl181:build jhammond$ mpiexec -n 1 ./a.out
>> application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
>> 
>> ===================================================================================
>> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
>> =   PID 61032 RUNNING AT alcfwl181.alcf.anl.gov
>> =   EXIT CODE: 1
>> =   CLEANING UP REMAINING PROCESSES
>> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>> ===================================================================================
>> 
>> 
>> 
>> On Thu, Feb 20, 2014 at 11:33 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>> 
>>>  Is there any way to turn off MPICH (and others) printing messages about MPI_Abort?  We have already prepared and presented useful error messages to the user about the situation and would like to avoid having these additional messages printed (that often make the situation look worse than it is)
>>> 
>>>   Thanks
>>> 
>>>  Barry
>>> 
>>> application called MPI_Abort(MPI_COMM_WORLD, 56) - process 0
>>> [cli_0]: aborting job:
>>> application called MPI_Abort(MPI_COMM_WORLD, 56) - process 0
>>> 
>>> ==================================================================mailto:discuss at mpich.org=================
>>> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
>>> =   EXIT CODE: 56
>>> =   CLEANING UP REMAINING PROCESSES
>>> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>>> ===================================================================================
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> discuss mailing list     discuss at mpich.org
>>> To manage subscription options or unsubscribe:
>>> https://lists.mpich.org/mailman/listinfo/discuss
>> 
>> 
>> 
>> -- 
>> Jeff Hammond
>> jeff.science at gmail.com
>> _______________________________________________
>> discuss mailing list     discuss at mpich.org
>> To manage subscription options or unsubscribe:
>> https://lists.mpich.org/mailman/listinfo/discuss
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140221/740532d6/attachment.html>


More information about the petsc-dev mailing list