Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Viet-Duc
Beginner
230 Views

MPI bad termination due to STOP

Jump to solution

We observed a peculiar behavior of Intel MPI with exit status emitted from STOP statement.

PROGRAM hello
    USE mpi
    IMPLICIT NONE

    INTEGER :: rank, size, ierror

    CALL MPI_INIT(ierror)
    CALL MPI_COMM_SIZE(MPI_COMM_WORLD, size, ierror)
    CALL MPI_COMM_RANK(MPI_COMM_WORLD, rank, ierror)

    PRINT *, 'rank', rank, ': Hello, World!'

    CALL MPI_FINALIZE(ierror)

    STOP 2
END

The exit status will be utilized for quick debugging purpose in our codes.

With Intel MPI 2019 Update 4, we received bad termination errors, for instance using 2 MPI ranks:

 rank           1 : Hello, World!
 rank           0 : Hello, World!
2
2

===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   RANK 0 PID 167623 RUNNING AT login03
=   EXIT STATUS: 2
===================================================================================

===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   RANK 1 PID 167624 RUNNING AT login03
=   EXIT STATUS: 2
===================================================================================

This behavior was not observed with previous versions of the library. We are not sure whether this is a bug of IMPI or an intended feature. 

Ideally, we are looking for a way to suppress this bad termination error.

Thanks.

0 Kudos
1 Solution
Anatoliy_R_Intel
Employee
230 Views

Hello,

 

Please check 2019 Update 5.  As far as I know this issue was fixed there.

--

Best regards, Anatoliy

View solution in original post

3 Replies
Anatoliy_R_Intel
Employee
231 Views

Hello,

 

Please check 2019 Update 5.  As far as I know this issue was fixed there.

--

Best regards, Anatoliy

View solution in original post

Viet-Duc
Beginner
230 Views

Thanks for your reply.

We have confirmed that upgrading to Update 5 resolved this issue.

Anatoliy_R_Intel
Employee
230 Views

Thank you!

Reply