[mpich-discuss] mpich2 1.0.8 on windows - domain required?

Tue Nov 4 19:12:01 CST 2008

Just being curious (this is my first post ...): have you already trued to
run MPICH2 with Linux ?

Best regards,

Marcus Vinicius.

2008/11/3, Thomas Blom <blomcode at gmail.com>:
>
> Thanks so much for your timely and detailed help.  Sorry that I became
> involved in other issues today and my reply is delayed.
>
> 1.  I removed mpich2 completely and reinstalled, and rebooted between and
> after these operations (as every superstitious windows-user has learned to
> do when problems occur).  I installed for everyone, as I have done
> previously.
>
> 2.  mpiexec -validate simply prints the statement "FAIL"
>
> 3.  I followed your directions for smpd and mpiexec in debug/verbose mode.
> Log files are attached.
>
> I will continue to play with this; thanks again for your continued help.
> My intuition is that this problem has to do with my having both renamed the
> machine and my user account just prior to setting this up a few days ago (to
> make the user accounts the same on both machines and make the machine-name
> less unwieldy to type).  But every other test I have performed to check the
> validity of the new names passes.
>
> -thomas blom, austin tx
>
> On Mon, Nov 3, 2008 at 11:22 AM, Jayesh Krishna <jayesh at mcs.anl.gov>wrote:
>
>>  Hi,
>>  Can you try re-installing MPICH2 making sure that MPICH2 is installed for
>> "Everyone" (the default is "Just me" - the user installing MPICH2) and
>> re-run mpiexec ?
>>  Can you validate the username/password registered on mb13 using the
>> "-validate" option of mpiexec (mpiexec -validate)?
>>
>>  If that does not work please provide us the debug logs for smpd/mpiexec,
>>
>> On mb13,
>>
>> 1) Stop any instances of smpd running on the machine using the command,
>> smpd -stop
>> 2) Run smpd in the debug mode & redirect the output to a log file, smpd -d
>> > smpd.log
>> 3) In another command window run mpiexec in debug/verbose mode and
>> redirect the output to a logfile, mpiexec -verbose -n 2 hostname >
>> mpiexec.log
>> 4) Provide us with the mpiexec/smpd log files.
>>
>> Regards,
>> Jayesh
>>
>>
>>  ------------------------------
>> *From:* mpich-discuss-bounces at mcs.anl.gov [mailto:
>> mpich-discuss-bounces at mcs.anl.gov] *On Behalf Of *Thomas Blom
>> *Sent:* Monday, November 03, 2008 10:41 AM
>>
>> *To:* mpich-discuss at mcs.anl.gov
>> *Subject:* Re: [mpich-discuss] mpich2 1.0.8 on windows - domain required?
>>
>> Yes, I've tried this.  To eliminate questions about the machine name
>> etc... I have
>>
>> 1.  go through network setup wizards again to establish that the machine
>> name is mb13 and the workgroup is LOGIC; disable  firewall.
>> (reboot)
>>
>> 1.5 Verify that I can share a folder on mb13, and from the other computer
>> can successfully map a drive to \\mb13\sharename -- this establishes that
>> mb13 is the recognized computer name.  And that other computers can reach it
>> at that name.
>>
>> 2.  uninstall mpich2 completely
>> 3.  install mpich2
>> (reboot)
>>
>> 4. mpi -register, and provide username/password of an account on the
>> machine that is a "computer administrator" (thomas)
>>
>> I still am unable to simply run mpiexec -n 2 hostname.... I get the same
>> "Credentials for thomas rejected connecting to mb13"
>>
>> I am able to run 'smpd -status' and it tells me that smpd is running on
>> mb13.
>>
>> Good grief... (my build from source & testing on two bsd-based macs took
>> about 15 minutes)
>>
>> -thomas
>>
>> On Mon, Nov 3, 2008 at 10:21 AM, Jayesh Krishna <jayesh at mcs.anl.gov>wrote:
>>
>>>  Hi,
>>>  Try re-registering your username(thomas)/password in mb13 using "mpiexec
>>> -register" command.
>>>
>>> Regards,
>>> Jayesh
>>>
>>>  ------------------------------
>>>  *From:* mpich-discuss-bounces at mcs.anl.gov [mailto:
>>> mpich-discuss-bounces at mcs.anl.gov] *On Behalf Of *Thomas Blom
>>> *Sent:* Monday, November 03, 2008 10:12 AM
>>> *To:* mpich-discuss at mcs.anl.gov
>>> *Subject:* Re: [mpich-discuss] mpich2 1.0.8 on windows - domain
>>> required?
>>>
>>>   The test command suggested (mpiexec -n 2 hostname) works fine on one
>>> of the machines.  On the other machine (both are winXP) I get the error:
>>>
>>> Credentials for thomas rejected connecting to mb13
>>> Aborting: Unable to connect to mb13
>>>
>>> This is the result of just running locally, not over a network!  In
>>> answer to the previous question, 'thomas' is not a domain user.  This is
>>> just two winXP machines on a local network that are part of the same
>>> "workgroup" but neither are part of any domain.
>>>
>>> I wonder if this has to do with my having changed the machine name on
>>> mb13 ... but I have since completely uninstalled and installed mpich2.  I
>>> left the default phrase "behappy" during this installation.  I then ran
>>> wmpiregister and entered my username and password (which I use to login to
>>> each machine sucessfully).
>>>
>>> I have tried to play with wmpiconfig, but it is a little difficult to
>>> understand how to use this.  I don't find any documentation for it.
>>>
>>> Thanks very much for any help....
>>>
>>> -thomas blom, austin tx
>>>
>>>
>>>
>>> On Mon, Nov 3, 2008 at 9:01 AM, Jayesh Krishna <jayesh at mcs.anl.gov>wrote:
>>>
>>>>  Hi,
>>>>  The machines don't have to be part of the same domain to be part of
>>>> your MPI job (This requirement is only for setups which use the SSPI
>>>> authentication mechanism to launch MPI jobs).
>>>>  Can you run a non-MPI command like hostname on the local machine ?
>>>>
>>>>    mpiexec -n 2 hostname
>>>>
>>>>  Is the user "thomas" a domain user ? In that case you should register
>>>> the username with the domainname (DOMAINNAME\USERNAME) when registering the
>>>> username (mpiexec -register) with mpiexec.
>>>>  Let us know if you still have problems.
>>>>
>>>> Regards,
>>>> Jayesh
>>>>
>>>>  ------------------------------
>>>> *From:* mpich-discuss-bounces at mcs.anl.gov [mailto:
>>>> mpich-discuss-bounces at mcs.anl.gov] *On Behalf Of *Thomas Blom
>>>> *Sent:* Sunday, November 02, 2008 8:45 AM
>>>> *To:* mpich-discuss at mcs.anl.gov
>>>> *Subject:* [mpich-discuss] mpich2 1.0.8 on windows - domain required?
>>>>
>>>>   Hello,
>>>>
>>>> I have just subscribed to the list to ask a question about mpich2 on
>>>> windows.  (I found the archives but don't see a way to search them).
>>>>
>>>> Is it a requirement that the windows computers participating in mpich2
>>>> be part of a windows domain?  I see things in the documentation that perhaps
>>>> imply this, but not state it outright.
>>>>
>>>> My computers are simply on a local network, and part of a "workgroup".
>>>> The smpd process manager can "see" the other systems to some extent, since
>>>> the result of
>>>>
>>>> smpd -status mb13    // mb13 is the hostname of my other windows pc
>>>>
>>>> correctly finds that smpd is running on my other host.  But executing
>>>> mpiexec and providing hostnames in a "machinefile" e.g.
>>>>
>>>> mpiexec -n 4 -machinefile machines echo %COMPUTERNAME%
>>>>
>>>> fails with:
>>>>
>>>> Credentials for thomas rejected connecting to mb13
>>>>
>>>>
>>>> I have taken care that the username/pass is identical on each machine,
>>>> the user is admin, etc.  I have followed steps I've found in various
>>>> documents about uninstalling/installing smpd and providing the identical
>>>> passphrase on each, running mpiexec -register, etc...
>>>>
>>>> Any ideas?  (Or is it just that I must be running on a domain, which I
>>>> cannot find concrete documentation about)
>>>>
>>>> thanks very much,
>>>> thomas blom in austin, tx
>>>>
>>>
>>>
>>
>
>

-- 
Marcus Vinicius
--
"Havendo suficientes colaboradores,
Qualquer problema é passível de solução"
Eric S. Raymond
A Catedral e o Bazar

"O passado é apenas um recurso para o presente"
Clave de Clau

"A melhor causa é sempre a próxima"
Evandro Lins e Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20081104/662985b9/attachment.htm>