Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Trapping fortran I/O errors leaving zombie mpiprocesses
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2010-01-28 14:00:12


On Jan 28, 2010, at 10:57 AM, Laurence Marks wrote:

> I am trying to find out if there is any way to create an error-handler
> or something else that will trap an error exit from the run-time
> library due to a fortran I/O error, or possibly some openmpi calls or
> options that will do the same thing.
>
> Let me expand a little. I am working with a very larger fortran 90
> code written by many people that uses mpi. While some of the
> read/write statements have an ERR= in them, not all do and it is a big
> job to add this to everyone (and not miss some). With some flavors of
> mpi (openmpi is one) if one process encounters an I/O error that
> process will crash, and the other ones can hang because no
> termination/abort signal is sent to them – this seems to be
> implementation dependent.

That's odd. What version of Open MPI are you using?

If one process dies prematurely in Open MPI (i.e., before MPI_Finalize), all the others should be automatically killed.

-- 
Jeff Squyres
jsquyres_at_[hidden]