My problem is slightly different: I have a product which executes as MPMD e.g. mpiexec -localonly -n 1 <main-prog>.exe : -n <X> <worker-prog>.exe
Whilst this is running, if VPN is disconnected, then the application terminates ("connection to proxy 0 failed", etc.)
I can reproduce using the following: mpiexec -localonly -n 4 IMB-MPI1.exe : -n 2 IMB-MPI1.exe
Currently we are running Intel MPI 5.0 (I know, very out-of-date - but there was a historical reason to do with dynamic spawning - no longer used) and will be looking to upgrade. I have actually installed 2019U7 to try but the issue still exists. The VPN disconnection problem for our users on laptops is almost a 'killer issue'. Any advice greatly appreciated.
As specified in the thread, you have mentioned the VPN disconnect issue has been resolved in the latest version.
As you were getting an error while using argument sets, we have tried with that too but haven't got any error after disconnecting VPN.
After upgrading to the MPI 2019u7 have you done the prerequisite steps as mentioned in Getting started guide(https://software.intel.com/content/www/us/en/develop/documentation/get-started-with-mpi-for-windows/...)?
If yes Could you please provide the command line so we can debug from our side.
Also if you were using Dynamic processes upgrade to the newer version 2019u8 in which PMI2 spawn support was added. (https://software.intel.com/content/www/us/en/develop/documentation/mpi-developer-reference-linux/top...)
Thx for getting back. We're in the middle of a release so I'm a little limited in time at the moment.
Like I said, when I executed the shipped exe as follows:
mpiexec -localonly -n 4 IMB-MPI1.exe : -n 2 IMB-MPI1.exe
and disconnected the VPN, then I got a crash.
However, executing the following works fine:
mpiexec -localonly -n 4 IMB-MPI1.exe
We have tried to reproduce the error in windows 10.
Could you please provide the debug info by setting I_MPI_DEBUG=5.
Also if possible please update to the latest version 2019u8 and check.
Thanks for the confirmation. It should also work with 2019u7 version too.
Anyway if your initial query has been answered please confirm so we can close the case.
Glad your problem is resolved.
If you require additional assistance from Intel, please start a new thread. Any further interaction in this thread will be considered community only