Re: [ptp-user] PBS Legacy RM Job Hanging

["Albert L. Rossi" <arossi@xxxxxxxxxxxxx>]

What platform are you on?  (don't think this should make any difference, but I thought I'd ask anyway ...)

Al
----- Albert L. Rossi <arossi@xxxxxxxxxxxxx> wrote:
> Oh, wait, I see you have the RMs from the test plugin in your list.  Something is very fishy here.
> 
> Al
> ----- Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:
> > Yes, I'm running with all of:
> > 
> > org.eclipse.ptp.rm.jaxb-feature
> > org.eclipse.ptp.rm.jaxb.pbs-feature
> > org.eclipse.ptp.rm.lml_jaxb-feature
> > org.eclipse.ptp.rm.lml-feature
> > org.eclipse.ptp.rm.jaxb.control.core
> > org.eclipse.ptp.rm.jaxb.control.ui
> > org.eclipse.ptp.rm.jaxb.core
> > org.eclipse.ptp.rm.jaxb.help
> > org.eclipse.ptp.rm.jaxb.pbs
> > org.eclipse.ptp.rm.jaxb.tests
> > org.eclipse.ptp.rm.jaxb.ui
> > org.eclipse.ptp.rm.lml_jaxb
> > org.eclipse.ptp.rm.lml.core
> > org.eclipse.ptp.rm.lml.da
> > org.eclipse.ptp.rm.lml.da.server
> > org.eclipse.ptp.rm.lml.monitor.core
> > org.eclipse.ptp.rm.lml.monitor.ui
> > org.eclipse.ptp.rm.lml.ui
> > 
> > Successfully built and loading in my run configuration according to the
> > launch.  But the only available RM's I see (from my new entirely fresh
> > checkout and build) are:
> > 
> > Demo Example
> > IBM LL
> > IBM PE
> > MPICH2
> > Namelist Example
> > Open MPI
> > Remote Launch
> > SLURM
> > 
> > Thanks,
> > Wyatt
> > 
> > On Mon, Jun 20, 2011 at 4:47 PM, Albert L. Rossi <arossi@xxxxxxxxxxxxx>wrote:
> > 
> > > If you are running the app from the workspace, make sure that
> > > org.eclipse.ptp.rm.jaxb.pbs, plus all the *.jaxb.* and *.lml.* plugins are
> > > indeed included in you Run Configuration ...
> > >
> > > Al
> > >
> > >
> > > ----- Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:
> > > > I just noticed, the legacy rm is showing up because I'm using a pretty
> > > old
> > > > workspace which contains the old packages.  I disabled them manually.
> > >  The
> > > > jaxb pbs plugins are in my workspace but the new pbs rms aren't showing
> > > up
> > > > in my new-rm list.
> > > >
> > > > =Wyatt
> > > >
> > > > On Mon, Jun 20, 2011 at 4:21 PM, Albert L. Rossi <arossi@xxxxxxxxxxxxx
> > > >wrote:
> > > >
> > > > > Wyatt,
> > > > >
> > > > > If you are using ptp-HEAD-all-committer.psf, the jaxb_lml resource
> > > manager
> > > > > along with the pbs feature should be there.
> > > > >
> > > > > When you go to choose a resource manager to add, you should see:
> > > > >
> > > > > PBS-generic-batch
> > > > > PBS-generic-interactive
> > > > >
> > > > > I thought Greg removed the legacy PBS from this .psf.  Maybe you need
> > > to
> > > > > update the .psf?
> > > > >
> > > > >
> > > > >
> > > > > Al
> > > > > ----- Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:
> > > > > > This is what was available in the RM list provided by the packages in
> > > the
> > > > > > HEAD psf file.  Is there a different RM project I should download
> > > that
> > > > > has a
> > > > > > more recent PBS RM?
> > > > > >
> > > > > > Thanks,
> > > > > > Wyatt
> > > > > >
> > > > > > On Mon, Jun 20, 2011 at 4:08 PM, Albert L. Rossi <
> > > arossi@xxxxxxxxxxxxx
> > > > > >wrote:
> > > > > >
> > > > > > > Wyatt,
> > > > > > >
> > > > > > > by legacy, I assume you mean 4.0 (Helios).
> > > > > > >
> > > > > > > I imagine this is some proxy issue (like maybe not parsing the
> > > submit
> > > > > lines
> > > > > > > and being able to send a JobStatusChanged event -- I think that's
> > > the
> > > > > old
> > > > > > > protocol).
> > > > > > >
> > > > > > > Is there some reason why you need to use 4.0?  It has been
> > > deprecated
> > > > > and I
> > > > > > > don't believe we are going to put any further effort into bug fixes
> > > for
> > > > > it
> > > > > > > ...
> > > > > > >
> > > > > > > Cheers,
> > > > > > >
> > > > > > > Al
> > > > > > > ----- Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:
> > > > > > > > Greetings,
> > > > > > > >
> > > > > > > > I'm trying to launch a job using the PBS Legacy Resource Manager.
> > >  It
> > > > > > > > detects the relevant nodes and the script it generates works
> > > > > correctly
> > > > > > > when
> > > > > > > > turned into a file and submitted with qsub on the command line.
> > > > >  However
> > > > > > > > when I attempt to run the job in Eclipse it hangs and has to be
> > > > > canceled.
> > > > > > > >
> > > > > > > >
> > > > > > > > The progress view has two tasks when it stops advancing
> > > > > > > >
> > > > > > > > "Remote Tools DStore Server (mist)" has its progress bar full and
> > > > > says
> > > > > > > > "Server running, cancel to terminate".
> > > > > > > >
> > > > > > > > The next task
> > > > > > > > "Launching ReallyRemoteC"
> > > > > > > > has its progress bar about 4/5 full and is stuck on the status
> > > > > > > "Initializing
> > > > > > > > remote services: Remote Tools: Submitting the job"
> > > > > > > >
> > > > > > > > I don't think it's a network problem because I can launch jobs
> > > using
> > > > > the
> > > > > > > > OpenMPI resource manager over the same Remote Tools connection.
> > >  The
> > > > > > > console
> > > > > > > > output is pasted below.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Wyatt Spear
> > > > > > > >
> > > > > > > >
> > > > > > > > !ENTRY org.eclipse.ptp.remote.core 4 0 2011-06-20 15:14:19.112
> > > > > > > > !MESSAGE Remote Tools DStore Server: Server running on:
> > > > > > > mist.cs.uoregon.edu
> > > > > > > > [NewRemoteC,
> > > /mnt/netapp/home1/wspear/RemoteWorkspace/ReallyRemoteC,
> > > > > [],
> > > > > > > > true,
> > > > > > > >
> > > > > > >
> > > > >
> > > #!/bin/bash\n\n#####################################################################\n##\sTemplate\sfor\sPBS\sBatch\sScript\sGenerated\sby\sPBS\sResource\sManager\n##\s\n##\sThis\stemplate\scontains\sall\sthe\sJob\sAttributes\srecognized\sas\svalid\n##\sby\sa\sgiven\sPBS\sproxy\sinstance.\n##\s\n##\sPlaceholders\s(@NAME@
> > > > > > > >
> > > > > > >
> > > > >
> > > )\sare\sincluded\sfor\sthe\sPBS\sJob\sAttribute\s\n##\snames\sas\sspecified\sby\sqsub,\splus\sthe\sfollowing\sinternal\svariables:\n##\n##\s-\senv\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s:\splace\sfor\sdefining\sextra\senvironment\n##\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\svariables\s(NB:\sshould\snot\sbe\sremoved)\n##\s-\sprependedBash\s\s\s\s\s\s\s\s\s\s\s:\sdynamically\schange\sarbitrary\sbash\s\n##\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\scommands\swhich\sshould\sprecede\sthe\s\n##\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\sexecution\sof\sthe\smain\sapplication\scode\n##\s-\smpiCommand\smpiOptions\s\s\s:\srun\sunder\sMPI\n##\s-\sexecutablePath\sprogArgs\s:\sthe\sactual\sapplication\n##\s-\spostpendedBash\s\s\s\s\s\s\s\s\s\s:\sdynamically\schange\sarbitrary\sbash\s\n##\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\scommands\swhich\sshould\sfollow\sthe\s\n##\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s!
 \s!
> > > > >  \s\
> > > > > > >
> > > > > > >
> > > > >
> > >  sexecution\sof\sthe\smain\sapplication\scode\n##\n##\sA\stemplate\scan\salso\sdirectly\scontain\sarbitrary\sshell\sscripting\s(not\s\n##\sto\sbe\sreplaced\svia\sthe\s'prepended'\sand\s'postpended'\splaceholders);\n##\sthese\slines\swill\sremain\sfixed\sand\swill\snot\sbe\sexposed\sthrough\n##\sthe\sLaunch\sTab\sfor\smodification\s(they\scan\showever\sbe\saltered\sby\s\n##\susing\sthe\sResource\sManager\sProperties\s"Edit"\sTab).\n##\n##\sNOTE:\sWe\sadvise\sremoving\seither\sthe\sncpus\sor\sthe\snodes\sresource,\n##\s\s\s\s\s\s\sdepending\son\sthe\sPBS\sconfiguration\s(nodes\sis\smore\scommon);\n##\s\s\s\s\s\s\sotherwise,\sthe\scorrect\svalue\smust\sbe\sset\son\sboth\sredundantly\n##\s\s\s\s\s\s\sin\sorder\sfor\sthe\sMPI\scomputation\sto\sbe\scorrect\s(and\s\n##\s\s\s\s\s\s\ssome\ssystems\smight\sreject\sa\sscript\swith\sboth\sset).\n#####################################################################\n#PBS\s-q\smist\n#PBS\s-N\sETest\n#PBS\s-l\sncpus=8\n#PBS\s-l\snode!
 s=!
> > > > >  1:ppn
> > > > > > >
> > > > > > >
> > > > >
> > >  =8\n#PBS\s-l\swalltime=00:30:00\n#PBS\s-V\s\n\ncd\s/mnt/netapp/home1/wspear/RemoteWorkspace/ReallyRemoteC\nmpiexec\s-n\s8\s/mnt/netapp/home1/wspear/RemoteWorkspace/ReallyRemoteC/NewRemoteC\s\n\n]
> > > > > > > >
> > > > > > > > !ENTRY org.eclipse.ptp.remote.core 4 0 2011-06-20 15:33:02.048
> > > > > > > > !MESSAGE Remote Tools DStore Server: DStore Server Starting...
> > > > > > > >
> > > > > > > > !ENTRY org.eclipse.ptp.remote.core 4 0 2011-06-20 15:33:02.252
> > > > > > > > !MESSAGE Remote Tools DStore Server: Server Started Successfully
> > > > > > > >
> > > > > > > > !ENTRY org.eclipse.ptp.remote.core 4 0 2011-06-20 15:33:02.252
> > > > > > > > !MESSAGE Remote Tools DStore Server: 43871
> > > > > > > >
> > > > > > > > !ENTRY org.eclipse.ptp.remote.core 4 0 2011-06-20 15:33:02.498
> > > > > > > > !MESSAGE Remote Tools DStore Server: Server running on:
> > > > > > > mist.cs.uoregon.edu
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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
> > >
> > >
> 
> _______________________________________________
> ptp-user mailing list
> ptp-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-user
>