[mpich-discuss] No requirement for smpd.exe in MPICH2-1.3.3

[Robert Hunter]

Jayesh,

Hi. I've  done a little more investigation into the registry entry for the -localonly option and here is what I have come up with. 

mpiexec is looking for HKEY_LOCAL_MACHINE->SOFTWARE->MPICH->SMPD . The SMPD key then needs to have a string entry named "binary" that has a data value pointing to the smpd.exe. If this registry entry is not available then "mpiexec.exe -localonly 2 cpi.exe" fails with the error message I emailed earlier in this thread. Once I manually create the registry entry "HKEY_LOCAL_MACHINE->SOFTWARE->MPICH->SMPD" mpiexec can then execute properly and it also adds a "process" key under the "HKEY_LOCAL_MACHINE->SOFTWARE->MPICH->SMPD" key. The process key then has keys for each process and the data in the keys is the path to cpi.exe or whatever mpi executable I'm trying to run.

Is this the expected behavior from mpiexec.exe with the -localonly option? The user's that I am targeting for running MPI codes compiled against MPICH do not have admin privileges, so this is a show stopper for me.

Thanks,

Bobby
On Mar 16, 2011, at 4:45 PM, Jayesh Krishna wrote:

> Hi,
>  When using "-localonly" option smpd should not access any reg entries that require admin privileges. Needs further investigation from my end (I know of at least one user who was able to successfully execute his jobs locally by just copying all the required exes/dlls with non-admin privileges).
> 
> -Jayesh
> 
> ----- Original Message -----
> From: "Robert Hunter" <Robert.M.Hunter at usace.army.mil>
> To: "Jayesh Krishna" <jayesh at mcs.anl.gov>
> Cc: mpich-discuss at mcs.anl.gov
> Sent: Tuesday, March 15, 2011 9:17:00 AM
> Subject: Re: [mpich-discuss] No requirement for smpd.exe in MPICH2-1.3.3
> 
> Jayesh,
> 
> 
> I believe the problem may lie in the fact that the smpd needs to write to the registry in HKEY_LOCAL_MACHINE, which I don't have permission to write into. I tried the same steps outlined below on a machine that I do have permission to write into HKEY_LOCAL_MACHINE and I was able to run.
> 
> 
> Do you know of anyway to override the default value of the registry key? In looking through the source I couldn't find any. Perhaps future versions could allow for registry entries to be written to HKEY_CURRENT_USER?
> 
> 
> Thanks,
> 
> 
> Bobby
> 
> 
> On Mar 10, 2011, at 4:55 PM, Jayesh Krishna wrote:
> 
> 
> 
> 
> 
> Hi,
> Try copying the *.dlls to C:\mpich2\bin and let us know if it works.
> 
> Regards,
> Jayesh
> 
> ----- Original Message -----
> From: "Robert Hunter" < Robert.M.Hunter at usace.army.mil >
> To: "Jayesh Krishna" < jayesh at mcs.anl.gov >
> Cc: mpich-discuss at mcs.anl.gov
> Sent: Wednesday, March 9, 2011 4:33:11 PM
> Subject: Re: [mpich-discuss] No requirement for smpd.exe in MPICH2-1.3.3
> 
> Jayesh,
> 
> 
> Thanks for the information regarding smpd.exe.
> 
> 
> I still have a question as to how I would run without installing smpd. I've tried the following:
> I copied smpd.exe, mpiexec.exe to a dir named C:\mpich2\bin, I then added this dir my to my PATH. I also copied mpich2mpi.dll, mpich2nemesis.dll, and cpi.exe to C:\mpich2 . I then unistalled mpich2-1.3.3rc1 and rebooted. Next I tried the following in the c:\mpich2 dir ".\bin\mpiexec.exe -localonly 2 cpi.exe" The following output is what I get:
> 
> C:\mpich2>.\bin\mpiexec.exe -localonly 2 .\cpi.exe
> Unknown option: -d
> Error while connecting to host, No connection could be made because the
> target machine actively refused it. (10061)
> Connect on sock (host=bhunter-lt.erdc.hpc.mil, port=8676) failed,
> exhaused all end points
> Unable to connect to 'bhunter-lt.erdc.hpc.mil:8676',
> sock error: Error = -1
> 
> ReadFile() failed, error 109
> unable to start the local smpd manager.
> 
> 
> C:\mpich2>
> 
> 
> 
> 
> Note: I don't have admin privileges on the machine.
> 
> 
> Thanks for any help.
> 
> 
> Bobby
> 
> 
> On Mar 3, 2011, at 11:18 AM, Jayesh Krishna wrote:
> 
> 
> 
> 
> 
> Hi,
> MPICH2 1.3.3 did not remove the requirement for smpd.exe .
> When using the "-localonly' option with mpiexec you do not need to have SMPD installed on the system. MPICH2 1.3.3 removed firewall issues when starting MPI jobs with the "-localonly" option.
> So you still need SMPD to be available, but you don't need to install SMPD or worry about firewall issues when running all MPI processes on the local node.
> 
> Regards,
> Jayesh
> 
> ----- Original Message -----
> From: "Robert Hunter" < Robert.M.Hunter at usace.army.mil >
> To: mpich-discuss at mcs.anl.gov
> Sent: Thursday, March 3, 2011 7:33:21 AM
> Subject: [mpich-discuss] No requirement for smpd.exe in MPICH2-1.3.3
> 
> I came across a note @ boinc.berkley.edu that stated mpich2-1.3.3 should remove the requirement for smpd.exe, as well as no firewall issues on Windows. I've downloaded and tried this method with the mpich-1.3.3r1-win-ia32 install and using the following command line "mpiexec -localonly -n 2 -channel nemesis:none cpi.exe" but it simply returns the following error "Uknown option -d". Will these functionality be included in the MPICH2-1.3.3 release?
> 
> Thanks,
> 
> Bobby
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20110323/da19238e/attachment.htm>