[mpich-discuss] mpdtrace cannot connect (cygwin & mpd), previous smpd remnants?

[Ralph Butler]

The short answer to the question is:  No, I do not know why it is  
failing.  Of course I do not have cygwin
to try it, and there is a good chance I could not reproduce it even if  
I did.  If he wants to gather some additional
info that might help to solve the problem, I have attached a temporary  
replacement for mpdlib.py that could be
used to replace the one in the installation.  It merely prints info  
about where the program gets to.  If we learn
something, from it, we could try 1 or 2 more iterations to narrow down  
the problem.
--ralph

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mpdlib.py
Type: text/x-python-script
Size: 66556 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20080401/ab0fd2fb/attachment.bin>
-------------- next part --------------




On TueApr 1, at Tue Apr 1 10:13AM, Jayesh Krishna wrote:

> Ralph,
>
> Do you know what the problem might be? This user is using Cygwin to  
> compile
> MPICH2(with mpd) on windows.
> He is able to run mpdcheck (mpdcheck -s, mpdcheck -c compname  
> portno) and
> get outputs as mentioned in the install guide. However he is not  
> able to run
> mpiexec or mpdtrace on his machine.
>
> ---
> mpd &
> [1] 2668
>
> ps
>      PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
>     2896       1    2896       2896  con 1008 18:03:07 /usr/bin/bash
>     2668    2896    2668       3772  con 1008 18:04:28 /usr/bin/ 
> python2.5
>     3256    2896    3256       3276  con 1008 19:03:38 /usr/bin/sh
>
> ls -l /tmp
> total 2048
> -rw-r--r-- 1 username None 2111 Mar 28 19:01 XWin.log
> -rw-r--r-- 1 username None   53 Mar 28 18:02 mpd2.console_username
>
> mpdtrace
> mpdtrace: cannot connect to local mpd (/tmp/mpd2.console_username);  
> possible
> causes:
>  1. no mpd is running on this host
>  2. an mpd is running but was started without a "console" (-n  
> option) In
> case 1, you can start an mpd on this host with:
>    mpd &
> and you will be able to run jobs just on this host.
> For more details on starting mpds on a set of hosts, see the MPICH2
> Installation Guide.
> ---
>
> Regards,
> Jayesh
>
>> -----Original Message-----
>> From: Ingo Bojak [mailto:I.Bojak at science.ru.nl]
>> Sent: Tuesday, April 01, 2008 3:33 AM
>> To: Jayesh Krishna
>> Subject: Re: [mpich-discuss] mpdtrace cannot connect (cygwin
>> & mpd), previous smpd remnants?
>>
>> Jayesh Krishna wrote:
>>>  Is your windows firewall turned on ? (If yes, 1. Stop any
>> instances
>>> of mpd running 2. Stop firewall 3.Try running "mpd&" & "mpiexec -n 1
>>> /bin/hostname".)
>>>  Can you see mpd running in the windows Task Manager ?
>>>
>> Turning off the firewall doesn't do a thing, mpiexec still
>> cannot connect. I cannot see "mpd" in the Task Manager, but
>> then I do not think that I should. I see "python2.5.exe" in
>> the Task Manager, which is what I see with "ps" in cygwin as
>> well (i.e., mpd is a python script, so I think it  is correct
>> that I see the executing python, not the script).
>> As mentioned previously, "python2.5.exe" is excepted in the
>> Windows firewall, so it makes no difference whether the
>> firewall is up or down for its running.
>>
>> I think it is significant that the mpdcheck server/client
>> *works*, but mpdtrace and mpiexec *doesn't*. Whatever is the
>> difference in their accessing mpd should explain the
>> problems. Unfortunately I have no idea what that difference may be.
>>
>> Cheers,
>> Ingo
>>
>>
>