Re: [ptp-dev] More PTP Milestone1A problems

[Dave Wootton <dwootton@xxxxxxxxxx>]

I installed the M3 build, the CDT 5.0.1
9/12 build and the Linux RDT server from the PTP 2.1 builds page. I'm now
able to create a remote C++ project on a Linux system running Eclipse on
my Windows XP system. I am able to open files on the remote system. I'm
not sure what the problems were before, but they seem to be fixed.
Dave

Chris Recoskie <recoskie@xxxxxxxxxx>
Sent by: ptp-dev-bounces@xxxxxxxxxxx

09/18/2008 10:05 AM

Please respond to
Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>

To	Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
cc
Subject	Re: [ptp-dev] More PTP Milestone1A problems

I can help some. I always connect to a running server
instance though so I can see my logging at the console. I haven't really
played much with the auto-launch stuff. If you are having problems getting
that to work and the help isn't cutting it, you could try pinging Dave
McKnight here in the Toronto lab as he is the dstore guy.

===========================

Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt

Greg
Watson <g.watson@xxxxxxxxxxxx>

Greg Watson <g.watson@xxxxxxxxxxxx>
Sent by: ptp-dev-bounces@xxxxxxxxxxx

09/18/2008 08:50 AM

Please respond to
Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>

To	Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
cc
Subject	Re: [ptp-dev] More PTP Milestone1A problems

Sorry for the confusion! Maybe Chris could help out with getting  
dstore working for RDT? I don't have a lot of experience with it.

Greg

On Sep 18, 2008, at 7:03 AM, Dave Wootton wrote:

> Greg
> The requirement for ssh-only connections for proxies is fine with
me  
> and
> satisfies any requirements for my testing of proxies for PTP 2.1.
I  
> might
> have been confused about what you were asking me, where I thought
you
> wanted me to try to set up a dstore connection between my windows
and
> AIX/Linux systems. That was what I was trying to do, and am having
> problems with getting that to work at all, even with using the remote
> c/c++ development view. The dstore problem isn't keeping me from  
> getting
> anything done, so we can look at that at your convenience.
> Dave
>
>
>
> Greg Watson <g.watson@xxxxxxxxxxxx>
> Sent by: ptp-dev-bounces@xxxxxxxxxxx
> 09/17/2008 08:27 PM
> Please respond to
> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>
>
> To
> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
> cc
>
> Subject
> Re: [ptp-dev] More PTP Milestone1A problems
>
>
>
>
>
>
> Ah, good!
>
> You may have missed one of my previous emails. Currently, PTP resource
> managers only work over ssh connections. You can use dstore
> connections for the Remote Development Tools (RDT), but you will have
> to create a separate connection for the resource manager. If you use
> the PTP new RM wizard, it will only create an RSE ssh connection.
>
> It's best to think of PTP and RDT as completely separate for now,
even
> though we plan to merge them together in the future.
>
> Hope this makes sense.
>
> Greg
>
> On Sep 17, 2008, at 4:30 PM, Dave Wootton wrote:
>
>> Greg
>> I tried three connections from my Windows system to my Linux pSeries
>> system, a 'Unix' connection using dstore, a 'Linux' connection
using
>> dstore, and a 'Linux' connection using ssh. I have the remote
c/c++
>> development perspective open, and am creating the connection by
right
>> clicking in the remote systems view, clicking new connection and
 
>> going
>> thru the wizards. I'm accepting whatever defaults there are on
each
>> page
>> other than selecting dstore/ssh as the connection type. After
the
>> connection is created, I try opening shell processes/my processes.
>> Only
>> the ssh connection works. Both dstore connections hang. I started
the
>> dstore server on the linux node (as root) by invoking daemon.pl
>> without
>> any arguments. The daemon starts by listening on port 4075. When
I
>> click
>> 'my processes', I see messages from the daemon that a new server
is
>> launched on port nnnnn but nothing more happens. If I shut down
>> Eclipse
>> and restart it, I get a message from the daemon 'Finished on port
>> nnnnn'.
>> Dave
>>
>>
>>
>> Greg Watson <g.watson@xxxxxxxxxxxx>
>> Sent by: ptp-dev-bounces@xxxxxxxxxxx
>> 09/17/2008 01:51 PM
>> Please respond to
>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>
>>
>> To
>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>> cc
>>
>> Subject
>> Re: [ptp-dev] More PTP Milestone1A problems
>>
>>
>>
>>
>>
>>
>> Dave,
>>
>> I think there are two potential causes here. One is that you're
>> running PTP under Windows, the other that you're trying to connect
to
>> an AIX box. Can you try connecting to a Linux box rather than
AIX
>> first?
>>
>> Greg
>>
>> On Sep 17, 2008, at 1:39 PM, Dave Wootton wrote:
>>
>>> Greg
>>> The RSE connection itself was working. It was only when I
tried to
>>> start
>>> the proxy that I had a problem where 'start proxy' would hang
 
>>> until I
>>> manually started the proxy on my AIX system. I had no problems
>>> editinng
>>> the RM and clicking the browse button.
>>>
>>> I'm not having any luck setting up a remote tools connection.
I'm
>>> still
>>> seeing hangs when I go thru the RM create wizard where Eclipse
is
>>> trying
>>> to establish a connectiion. If I click the cancel button in
the
>>> connection
>>> popup, the cancel button grays out but Eclipse is hung and
I have to
>>> kill
>>> it with the windows task manager. I have a dstore daemon (downloaded
>>> from
>>> the RSE 3.0 downloads) that I'm running on my AIX system,
invoked as
>>> root
>>> by running 'daemon.pl')
>>>
>>> I reinstalled my Ganymede Eclipse clean, reinstalling the
PTP 2.1 M2
>>> build, the CDT 5.0.1 build dated 9/5, and RSE 3.0 runtime.
I then
>>> checked
>>> out all the PTP code from CVS HEAD then tried to run a 2nd
eclipse
>>> session. I try to open the PTP runtime perspective perspective
in
>>> that
>>> second session and get a popup 'Problems opening perspective
>>> org.eclipse.ptp.ui.PTPRunPerspective
>>> Dave
>>>
>>>
>>>
>>> Greg Watson <g.watson@xxxxxxxxxxxx>
>>> Sent by: ptp-dev-bounces@xxxxxxxxxxx
>>> 09/17/2008 10:03 AM
>>> Please respond to
>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>>
>>>
>>> To
>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>> cc
>>>
>>> Subject
>>> Re: [ptp-dev] More PTP Milestone1A problems
>>>
>>>
>>>
>>>
>>>
>>>
>>> Dave,
>>>
>>> Can you also verify that the RSE connection is working by
editing
>>> the RM
>>> and clicking on the "Browse" button?
>>>
>>> Greg
>>>
>>> On Sep 17, 2008, at 8:52 AM, Greg Watson wrote:
>>>
>>> Dave,
>>>
>>> Could you try with a Remote Tools connection instead of an
RSE
>>> connection?
>>> Do you see the same problem?
>>>
>>> Greg
>>>
>>> On Sep 16, 2008, at 9:47 PM, Dave Wootton wrote:
>>>
>>>
>>> Greg
>>> I just verified that I don't have the manual launch checkbox
>>> checked. I
>>> had the same problem. I tried clicking the manual launch checkbox
to
>>> see
>>> what would happen. That also required  me to start the
proxy
>>> manually, as
>>> I expected.
>>>
>>> I had my RSE connection set up without a stored password.
If I had
>>> the
>>> manual launch checkbox unchecked, then when I tried to start
the
>>> proxy I
>>> would get a password prompt that I responded to. If the manual
 
>>> launch
>>> checkbox checked, I would not see the password prompt. In
both
>>> cases, the
>>> proxy had to be started manually.
>>>
>>> I now have a stored password in my RSE connection and now
when the
>>> manual
>>> launch checkbox is unchecked, I don't see the password prompt,
but I
>>> still
>>> have to start the proxy manually.
>>> Dave
>>>
>>>
>>> Greg Watson <g.watson@xxxxxxxxxxxx>
>>> Sent by: ptp-dev-bounces@xxxxxxxxxxx
>>> 09/16/2008 10:34 AM
>>>
>>> Please respond to
>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>>
>>>
>>>
>>> To
>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>> cc
>>>
>>> Subject
>>> Re: [ptp-dev] More PTP Milestone1A problems
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Dave,
>>>
>>> Thanks for finding that bug. Working on a fix now. I know
this is a
>>> silly
>>> question, but you don't have the manual launch checkbox selected
do
>>> you?
>>>
>>> Greg
>>>
>>> On Sep 13, 2008, at 10:40 AM, Dave Wootton wrote:
>>>
>>>
>>> I think I figured out why I was getting a hang in trying to
start my
>>> proxy
>>> using a ssh-only RSE connection. It turns out that there is
a null
>>> pointer
>>> exception at line 112 of RDEProcessBuilder because the directory()
>>> method
>>> is returning null. It seems taht the constructor for
>>> AbstractRemoteProcessBuilder is called, but the directory(IFileStore
>>> directory) method is never called.  If I change the try
block to
>>> try {
>>>                  
  IFileStore dir;
>>>                  
  dir = directory();
>>>                  
  if (dir == null) {
>>>                  
          hostShell = shellService.runCommand(
>>> "/home/wootton", remoteCmd, env,new NullProgressMonitor());
 //$NON-
>>> NLS-1$
>>>
>>>                  
  }
>>>                  
  else {
>>>                  
          hostShell =
>>> shellService.runCommand(directory().toURI().getPath(), remoteCmd,
>>> env,new
>>> NullProgressMonitor());  //$NON-NLS-1$
>>>                  
  }
>>>             }
>>>
>>> I'm not sure that's the right way to fix it, but it seems
to me it
>>> should
>>> work for this specific case since the proxy is invoked by
absolute
>>> path.
>>> I get past the null pointer exception and that particular
hang. I
>>> end up
>>> still hung a little later though I get the following output
in the
>>> console
>>> for my first eclipse session
>>> PE@k17sf2p03ProxyRuntimeClient - firing up proxy, waiting
for
>>> connection.
>>> Please wait!  This can take a minute . . .
>>> PROXY_SERVER path = 'PE@k17sf2p03'
>>> sessionCreate(0,0)
>>> bind(0.0.0.0/0.0.0.0:0)
>>> port=4251
>>> Launch command:
>>> [/home/wootton/pxy/org.eclipse.ptp.rm.ibm.pe.proxy/ptp_ibmpe_proxy,
>>> --proxy=tcp, --host=9.65.138.73, --port=4251, --debug=1, --
>>> trace=Detail,
>>> --suspend_at_startup]
>>> accept thread starting...
>>> PE@k17sf2p03: Last login: Sat Sep 13 10:23:50 2008 from
>>> sig-9-65-138-73.mts.ibm.com
>>> PE@k17sf2p03: cd /home/wootton
>>> PE@k17sf2p03:
>>> PE@k17sf2p03: echo $PWD'>'
>>> PE@k17sf2p03:
>>> PE@k17sf2p03: -bash-3.1$ cd /home/wootton
>>> PE@k17sf2p03: -bash-3.1$
>>> PE@k17sf2p03: -bash-3.1$ echo $PWD'>'
>>> PE@k17sf2p03: /home/wootton>
>>> PE@k17sf2p03: -bash-3.1$
>>> PE@k17sf2p03: -bash-3.1$
>>> PE@k17sf2p03ProxyRuntimeClient: Waiting on accept.
>>>
>>> At that point, proxy startup is hung. I don't see any sign
that my
>>> proxy
>>> was run. If I paste the command 'Lauch command:', minus the
commas
>>> and run
>>> that on my remote system, then the proxy startup completes
and I
>>> have a
>>> running proxy. At that point, I can run a PE job and everything
 
>>> works
>>> normally.
>>> Dave
>>>
>>> Greg Watson <g.watson@xxxxxxxxxxxx>
>>> Sent by: ptp-dev-bounces@xxxxxxxxxxx
>>> 09/12/2008 08:30 AM
>>>
>>> Please respond to
>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>>
>>>
>>>
>>> To
>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>> cc
>>>
>>> Subject
>>> Re: [ptp-dev] More PTP Milestone1A problems
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Sorry for the confusion. I'll update the release notes as
soon as I
>>> get a chance.
>>>
>>> It's best to consider PTP and RDT as completely separate for
the
>>> moment. If you're using RSE, then you'll need an ssh-only
connection
>>> for PTP and a dstore connection for RDT. We're going to need
to work
>>> out how to make this more transparent in the future, but for
now you
>>> can either create both connections using the RSE connection
manager,
>>> or use the PTP RM wizard to create the ssh one.
>>>
>>> Greg
>>>
>>> On Sep 12, 2008, at 8:22 AM, Dave Wootton wrote:
>>>
>>>> Chris
>>>> My rse connection was ssh only. I set up a new rse connection
using
>>>> dstore
>>>> only (even though the RSE connection setup dialog has
checkboxes  
>>>> for
>>>> dstore, ssh, etc, I can only pick one) and set up a dstore
server  
>>>> on
>>>> my
>>>> Linux node by running daemon.pl 4075 4200-4203
>>>> I can see connect messages logged on my Linux node but
if I try to
>>>> do
>>>> something simple like show my processes in the RSE prespective
>>>> remote
>>>> systems view, that request hangs and eventually times
out. I am  
>>>> able
>>>> to
>>>> get xclock to work displaying on my Windows machine and
don't seem
>>>> to be
>>>> having any other network problems.
>>>>
>>>> I don't know if I'm still having firewall or network issues.
I  
>>>> won't
>>>> be
>>>> back in the office with time to try this without firewalls
until
>>>> next Wed.
>>>>
>>>> Greg
>>>> Will the proxy startup work with a ssh-only rse connection
or is
>>>> dstore
>>>> required for that too? I was able to start bthe proxy
with a ssh  
>>>> rse
>>>> connection in PTP 2.0 a while ago, don't know if anything
is
>>>> changed.
>>>>
>>>> Dave
>>>>
>>>>
>>>>
>>>> Chris Recoskie <recoskie@xxxxxxxxxx>
>>>> Sent by: ptp-dev-bounces@xxxxxxxxxxx
>>>> 09/11/2008 10:09 PM
>>>> Please respond to
>>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>>>
>>>>
>>>> To
>>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>>> cc
>>>>
>>>> Subject
>>>> Re: [ptp-dev] More PTP Milestone1A problems
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Is your RSE connection SSH only? The remote indexing stuff
requires
>>>> dstore...
>>>>
>>>> ===========================
>>>>
>>>> Chris Recoskie
>>>> Team Lead, IBM CDT Team
>>>> IBM Toronto
>>>> http://www.eclipse.org/cdt
>>>>
>>>> Dave Wootton <dwootton@xxxxxxxxxx>
>>>>
>>>>
>>>> Dave Wootton <dwootton@xxxxxxxxxx>
>>>> Sent by: ptp-dev-bounces@xxxxxxxxxxx
>>>> 09/11/2008 09:59 PM
>>>>
>>>> Please respond to
>>>> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>>>>
>>>>
>>>>
>>>>
>>>> To
>>>>
>>>> ptp-dev@xxxxxxxxxxx
>>>>
>>>> cc
>>>>
>>>>
>>>> Subject
>>>>
>>>> [ptp-dev] More PTP Milestone1A problems
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I tried the PTP milestone1 build again tonight and got
a little
>>>> farther
>>>> with trying to create a new remote project. This time
when I tried
>>>> to use
>>>> the new remote project wizard, I was able to choose the
remote  
>>>> tools
>>>> filesystem and click the browse button next to the location
text
>>>> field on
>>>> the first wizard page. This time, I was able to select
a connection
>>>> name
>>>> from the dropdown at the top of the browse directory dialog,
and
>>>> then
>>>> browse my home directory on my remote Linux system and
select a
>>>> directory
>>>> on hat system. However, as I tried to advance thru the
wizard pages
>>>> I got
>>>> a message in the PDE error log window that the directory
path I
>>>> selected
>>>> could not be opened, and the finish button for the wizard
never was
>>>> enabled. The odd thing was that the pathname that showed
up in the
>>>> error
>>>> message had '\' as directory delimiters instead of '/'.
My eclipse
>>>> GUI is
>>>> running on a windows XP system so I'm wondering if pathnames
are
>>>> being
>>>> sent to the Linux system with '\' in the path name.
>>>>
>>>> I wasn't sure why this was failing so I downloaded the
M1A build.
>>>> Now when
>>>> I select browse in the new remote project wizard and then
click a
>>>> connection name in the browse directory dropdown, I get
a progress
>>>> dialog
>>>> but it freezes at about the halfway point and the connection
 
>>>> doesn't
>>>> complete within a couple minutes. At that point I canceled
the
>>>> progress
>>>> dialog.
>>>>
>>>> Another problem that I have been seeing, and which still
happens in
>>>> the
>>>> M1A build is that if I have a PE proxy running when I
shut down
>>>> eclipse,
>>>> then the next time I start Eclipse, where I have a different
IP
>>>> address
>>>> (because I've dropped my VPN connection and then reconnected),
then
>>>> when
>>>> PTP tries to restart the proxy, it fails and the icon
for that  
>>>> proxy
>>>> is
>>>> blue. At that point, I can't do anything with the proxy.
I shot  
>>>> down
>>>> Eclipse and start again, and the proxy icon is now gray
(inactive).
>>>> If I
>>>> fix the local address for proxy connection in the resource
manager
>>>> wizard
>>>> so it matches my current IP address, I can start the proxy
and
>>>> everything
>>>> is fine. If there was a way to reset the state of the
proxy icons  
>>>> in
>>>> the
>>>> resource manager wizard so that it wasn't blue, I wouldn't
have to
>>>> restart
>>>> Eclipse to fix the problem.
>>>>
>>>> I have what I think is a working RSE connection. If I
open the
>>>> Remote
>>>> System Explorer perspective and open Sftp files or shell
processes
>>>> in the
>>>> tree in the remote systems view, I can see files and processes
>>>> appear in
>>>> the view. I switched to the PTP runtime view and tried
to create a
>>>> resource manager using the same RSE connection. The first
problem  
>>>> is
>>>> that
>>>> if I change the remote service provider to RSE, then the
browse
>>>> button
>>>> next to the proxy path edit filed does't do anything.
If I select
>>>> local as
>>>> the remote service provider, then I get a file selector
dialog. I
>>>> switched
>>>> remote service provider back to RSE and pasted in the
full path  
>>>> name
>>>> to my
>>>> proxy and filled in the other fields in the wizard and
clicked
>>>> finish.
>>>> Then I tried to start the proxy. I get a progress dialog
for a
>>>> couple
>>>> seconds and then I get a popup dialog with a message 'Failed
to
>>>> start
>>>> resource manager' and the proxy icon goes to the blue
state.
>>>>
>>>> Dave_______________________________________________
>>>> ptp-dev mailing list
>>>> ptp-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>> _______________________________________________
>>>> ptp-dev mailing list
>>>> ptp-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> ptp-dev mailing list
>>>> ptp-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>>
>>>
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>
>>>
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>
>>
>> _______________________________________________
>> ptp-dev mailing list
>> ptp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>
>>
>> _______________________________________________
>> ptp-dev mailing list
>> ptp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>

_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev

_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev