[mpich-discuss] Blocking Receive

[Pavan Balaji]

Ah, it's a strerror output. Copy-pasting the error message helps :-).

Looks like one of your processes died abnormally, which caused MPI to barf.

  -- Pavan

On 08/26/2010 03:08 PM, Hiatt, Dave M wrote:
> Here’s the message
>
> Fatal error in MPI_Recv: Other MPI error, error stack:
>
> MPI_Recv(187).............................:
> MPI_Recv(buf=0000000002D50044, count=2000000, MPI_BYTE,
> src=MPI_ANY_SOURCE, tag=MPI_ANY_TAG, MPI_COMM_WORLD,
> status=0000000003120B10) failed
>
> MPIDI_CH3i_Progress_wait(215).............: an error occurred while
> handling an event returned by MPIDU_Sock_Wait()
>
> MPIDI_CH3I_Progress_handle_sock_event(420):
>
> MPIDU_Sock_wait(2606).....................: The specified network name
> is no longer available. (errno 64)
>
> job aborted:
>
> rank: node: exit code[: error message]
>
> 0: REL001MW430C9B.nam.nsroot.net: 123: Fatal error in MPI_Recv: Other
> MPI error, error stack:
>
> MPI_Recv(187).............................:
> MPI_Recv(buf=0000000002D50044, count=2000000, MPI_BYTE,
> src=MPI_ANY_SOURCE, tag=MPI_ANY_TAG, MPI_COMM_WORLD,
> status=0000000003120B10) failed
>
> MPIDI_CH3i_Progress_wait(215).............: an error occurred while
> handling an event returned by MPIDU_Sock_Wait()
>
> MPIDI_CH3I_Progress_handle_sock_event(420):
>
> MPIDU_Sock_wait(2606).....................: The specified network name
> is no longer available. (errno 64)
>
> 1: REL001MW430C9B.nam.nsroot.net: -1073740777: process 1 exited without
> calling finalize
>
> “People get held back by the voice inside em” – K’naan – In the Beginning
>
> *Dave M. Hiatt*
>
> Director, Risk Analytics
>
> CitiMortgage
>
> 1000 Technology Drive
> O'Fallon, MO 63368-2240
>
> Telephone: 636-261-1408
>
>
>
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss

-- 
Pavan Balaji
http://www.mcs.anl.gov/~balaji