Link Copied
Hi,
Could you please follow these steps:
1. If you are using Intel MPI 2010 we advise you to use Intel MPI 2021.11 because there is a problem with paths containing spaces in the older version.
2. Could you please install and enable the winrm service (you can check if it is enabled with "get-service winrm" in PowerShell) if you haven't done this.
3. Add all relevant nodes to the list of TrustedHosts e.g. in Windows PowerShell with
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "<comma-separated list of hosts>"
4. Test the visibility of the hosts in PowerShell with
Invoke-Command -ComputerName <comma-separated list of hosts> -ScriptBlock {hostname}
if the command above fails, it will mention what's missing. You will have to follow these instructions.
5. Once the above command above works, you can proceed to the next item.
Call setvars.bat from Intel MPI from cmd.exe not from PowerShell!
Test it from cmd.exe with the following command:
mpiexec -ppn 1 -hosts <comma-separated list of hosts> hostname
Here is a screenshot for your reference.
Thanks & Regards,
Shaik Rabiya
Hello @RabiyaSK_Intel
I followed your instructions and completed steps 1-3 without any issues. However when I tried to run Step 4, I was met with the following error:
Command: Invoke-Command -ComputerName ATS, ATS1, ATS2 -ScriptBlock {hostname}
Output:
[ATS1] Connecting to remote server ATS1 failed with the following error message: WinRM client cannot process the request. The following error occured while using Kerberos authentication: Cannot find the computer ATS1. Verify that the computer exists on the network and that the name provided is spelled correctly.
[ATS2] Connecting to remote server ATS2 failed with the following error message: WinRM client cannot process the request. The following error occured while using Kerberos authentication: Cannot find the computer ATS2. Verify that the computer exists on the network and that the name provided is spelled correctly.
ATS
Same error message again for ATS2 as well.
As the host was able to succesfully ping ATS1 and ATS2, I knew there was no error in the computer/host name or the connectivity.
So after spending a lot of time googling I was able to solve the issue.
The command had to be modified as below:
Command: Invoke-Command -ComputerName ATS, ATS1, ATS2 -Credential Domain\Username -ScriptBlock {hostname}
This brings up a pop-up window like this where the password is to be entered
and we get the successful output as
ATS
ATS1
ATS2
So we need to provide the domain and username explicitly with the command line instructions.
Now, I tried to follow your remaining set of instructions of calling setvars.bat from cmd.exe and then executing mpiexec -ppn 1 -hosts ATS, ATS1, ATS2 hostname and ended up with the same error as before.
[proxy:0:0@ATS] HYD_spawn (..\windows\src\hydra_spawn.c:282): unable to create process ATS1,ATS2 hostname (error code 2)
[proxy:0:0@ATS] launch_processes (proxy.c:596): error creating process (error code 2). The system cannot find the file specified.
[proxy:0:0@ATS] main (proxy.c:969): error launching_processes
[mpiexec@ATS] check_downstream_work_complition (mpiexec.c:1303): downstream from host ATS exited abnormally
[mpiexec@ATS] check_downstream_work_complition (mpiexec.c:1307): trying to close other downstreams
[mpiexec@ATS] HYD_sock_write (..\windows\src\hydra_sock.c:387): write error (errno = 2)
[mpiexec@ATS] wmain (mpiexec.c:2275): assert (pg->intel.exitcodes != NULL) failed
[mpiexec@ATS] HYD_sock_write (..\windows\src\hydra_sock.c:387): write error (errno = 2)
So, back to the original error.
But based on the experience with the Invoke-Command, we probably need to provide domain and username along with the password to the mpiexec command. This was very easy to do with the mpiexec -register command earlier. But it produces the following error:
[mpiexec@ATS] match_arg (arg\hydra_arg.c:91): unrecognized argument register
[mpiexec@ATS] Similar arguments:
[mpiexec@ATS] rr
[mpiexec@ATS] r
[mpiexec@ATS] HYD_arg_parse_array (arg\hydra_arg.c:128): argument matching returned error
[mpiexec@ATS] mpiexec_get_parameters (mpiexec_params.c:1359): error parsing input array
[mpiexec@ATS] wmain (mpiexec.c:1893): error parsing parameters
The -register option is no longer recognized even though it is still listed in mpiexec -help. I feel this is what is preventing the command from successfully running and Intel MPI developers need to provide a quick patch or workaround to get it to work. Looking forward to an update on this.
