[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Condor-users] Running Grid Monitor in debug?

I am currently trying to use Condor-G to submit
jobs to a gt2 jobmanager-pbs resource.  My test job runs fine
on some remote jobmanager-pbs resources that are known to be good.
But on the new one I am configuring, the symptom is the following:

Condor-G submits the job, in my desktop queue it shows as "idle"
on the remote gt2/pbs site, the jobmanager-pbs exits immediately
as it should, the job is submitted, I can see it running in pbs,
the stdout and stderr get put in the directory where they should,
but condor-G never detects that the job is running, nor that it
has completed, and the stderr never gets put back where it should.
globus-job-status reports that the job is complete as soon as it is submitted.

I suspect that there's something wrong in the polling interface
where the condor grid monitor (which is submitted via a fork to
the gt2/pbs host) doesn't correctly talk to the jobmanager-pbs to
poll the job, because it never sees any jobs running on the remote host.
But the only way to do this is to debug somehow.
The grid monitor has got a debug flag but the job that is
submitting it is submitted from deep within the guts of condor
and I don't see any way to enable the debug flag.  Does anyone
else know how to enable the debug flag, and/or to run
the grid monitor interactively?   Instructions on how to do
so were at one point posted to this list but I can't find them.
strace on the existing grid monitor doesn't tell me anything.

Steve Timm

Steven C. Timm, Ph.D  (630) 840-8525  timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team