Difference between revisions of "Tracing Jobs"
From GridPP Wiki
Line 1: | Line 1: | ||
+ | = Tracing jobs on typical GridPP site config = | ||
+ | |||
== ARC CE/HTCondor == | == ARC CE/HTCondor == | ||
+ | |||
+ | This job tracing example is based on HTCondor/ARC CE combination at Oxford. | ||
+ | |||
+ | ARC CE logs does not provide much useful information but HTCondor provides detailed logs which can be easily searched. I am assuming that we know the DN of the user. | ||
+ | |||
+ | HTCondor logs can be accessed through either '''condor_q''' or '''condor_history'''. '''Condor_q''' provides job information about the current jobs in the queue and '''condor_history''' gives information about jobs which has been finished. | ||
+ | |||
== SGE/Cream == | == SGE/Cream == |
Revision as of 13:48, 28 February 2019
Tracing jobs on typical GridPP site config
ARC CE/HTCondor
This job tracing example is based on HTCondor/ARC CE combination at Oxford.
ARC CE logs does not provide much useful information but HTCondor provides detailed logs which can be easily searched. I am assuming that we know the DN of the user.
HTCondor logs can be accessed through either condor_q or condor_history. Condor_q provides job information about the current jobs in the queue and condor_history gives information about jobs which has been finished.