Re: [ptp-user] parallel application run failure

[Brett Bode <bbode@xxxxxxxxxxxxx>]

Thanks Dave. The bug id is https://bugs.eclipse.org/bugs/show_bug.cgi?id=286575

I think generating more error reporting would be a very useful step as  
well. I saw some useful errors emitted in the trace output. Can you  
elevate those into the error log in the gui?

Brett
On Aug 13, 2009, at 3:35 PM, Dave Wootton wrote:

> Brett
> That's good news. While not strictly an error, I need to do a better  
> job
> of matching up the hostnames in the hostlist file to the internal list
> generated by PE. I have a couple ideas how to approach this. Can you
> create a bug report for this?
> Dave
>
>
>
> From:
> Brett Bode <bbode@xxxxxxxxxxxxx>
> To:
> PTP User list <ptp-user@xxxxxxxxxxx>
> Date:
> 08/13/2009 02:45 PM
> Subject:
> Re: [ptp-user] parallel application run failure
> Sent by:
> ptp-user-bounces@xxxxxxxxxxx
>
>
>
> Thanks to Greg and Dave I now have this working.
>
> The key was enabling the tracing as Greg's email laid out finally gave
> me the error message I needed:
> PE@xxxxxxxxxxxxxxxxxxxxxxx: 08/13 13:23:48 T(256) Error: Node f10n12
> not found in node list
>
> My hostlist was using the "primary" name for the login node (bp-
> login1). That is the name you ssh to and what hostname returns (and
> even shows up in LL). Thus I am surprised to see that PE must have
> translated that name to the internal switch name of f10n12. If I
> switch to that name in the hostlist it works properly.
>
> Seems like an opportunity for better error reporting... :-)
>
> Brett
>
> On Aug 12, 2009, at 3:43 PM, Greg Watson wrote:
>
> > Dave,
> >
> > > Greg, if this doesn't solve the problem, I need to see the messages
> > > that
> > > are logged by the PTP trace and by the PE  proxy. Can you remind me
> > > what
> > > file I have to edit and what options to set within that file to
> > > turn on
> > > this tracing?
> >
> > The easiest thing to do is use the Tracing tab on the Eclipse
> > Application run configuration. Enable debug/proxy/protocol/tracing
> > under org.eclipse.ptp.core.
> >
> > If you're not using a runtime Eclipse, you need to start Eclipse
> > with the -debug flag. It will give you a message about not being
> > able to load a debug options file. You need to create this file in
> > the specified location with the following contents (or whatever you
> > want to enable), then re-run "eclipse -debug":
> >
> > org.eclipse.ptp.core/debug=true
> > org.eclipse.ptp.core/debug/proxy/protocol/tracing=true
> > org.eclipse.ptp.core/debug/proxy/client/tracing=true
> > org.eclipse.ptp.core/debug/proxy/server/debug_level=1
> > org.eclipse.ptp.core/debug/rm/tracing=true
> >
> > Greg
> > _______________________________________________
> > ptp-user mailing list
> > ptp-user@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/ptp-user
>
> _______________________________________________
> ptp-user mailing list
> ptp-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-user
>
>
>
> _______________________________________________
> ptp-user mailing list
> ptp-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-user