Intel® MPI Library
Get help with building, analyzing, optimizing, and scaling high-performance computing (HPC) applications.
2161 Discussions

Nested MPI process failed with GetParentPort error

CALUGARU_D_
Beginner
775 Views

Hello,

we are trying to execute a tricky code with intel mpi 5.0.2.044.

We have a main program executed via

mpirun -n 1 Exec_main

This main program makes system call to an external shell script that does

mpirun -genv I_MPI_DEBUG 5 -n 4 ExecSub

When executing the external shell manually, everything is fine.

When launching the shell from the main executable, we have the following error :

[0] MPI startup(): Multi-threaded optimized library
[2] MPI startup(): shm and tcp data transfer modes
[3] MPI startup(): shm and tcp data transfer modes
[0] MPI startup(): shm and tcp data transfer modes
[1] MPI startup(): shm and tcp data transfer modes
Fatal error in PMPI_Init_thread: Other MPI error, error stack:
MPIR_Init_thread(784).......:
MPID_Init(1452).............: spawn process group was unable to obtain parent port name from the channel
MPIDI_CH3_GetParentPort(369):  PMI2 KVS_Get failed: -1
Fatal error in PMPI_Init_thread: Other MPI error, error stack:
MPIR_Init_thread(784).......:
MPID_Init(1452).............: spawn process group was unable to obtain parent port name from the channel
MPIDI_CH3_GetParentPort(369):  PMI2 KVS_Get failed: -1
Fatal error in PMPI_Init_thread: Other MPI error, error stack:
MPIR_Init_thread(784).......:
MPID_Init(1452).............: spawn process group was unable to obtain parent port name from the channel
MPIDI_CH3_GetParentPort(369):  PMI2 KVS_Get failed: -1
Fatal error in PMPI_Init_thread: Other MPI error, error stack:
MPIR_Init_thread(784).......:
MPID_Init(1452).............: spawn process group was unable to obtain parent port name from the channel
MPIDI_CH3_GetParentPort(369):  PMI2 KVS_Get failed: -1

Do you have any clue on how to understand and solve this issue ?

Best regards

 

0 Kudos
1 Reply
Dmitry_S_Intel
Moderator
775 Views

Hi,

Version 5.0.2 is pretty old, can you try with released 2017 Update 2.

--

Dmitry

0 Kudos
Reply