Re: [HTCondor-users] Use of debug statement in machine configuration file

Mailing List Archives Public Access	UW Madison Computer Sciences Department Computer Systems Lab

On Feb 25, 2021, 9:17 AM -0500, Greg Thain <gthain@xxxxxxxxxxx>, wrote:

*** Attention: This is an external email. Use caution responding, opening attachments or clicking on links. ***
Hello Gerard:

The classad debug() function prints debugging information to the log when the classad is evaluated. So, if you want to debug a slot's START _expression_, you can append to the start _expression_ with

START = debug($(START))

in the startd's config file.

To debug a job's requirements, you could write in the submit file

requirements = debug(whatever the requirements were..)

-greg

On 2/25/21 8:01 AM, Weatherby,Gerard wrote:
I am trying to understand how to use the AnyType debug(AnyType _expression_)feature documented at https://htcondor.readthedocs.io/en/latest/misc-concepts/classad-mechanism.html.

I have added the following to a file in /etc/condor/config.d:

ALL_DEBUG = D_FULLDEBUG D_COMMAND
SCHED_DEBUG = D_FULLDEBUG
DString = debug(Requirements)
DString2 = debug("unimarker")

and condor_config_val -schedd DString (and DString2) shows the expected results. Iâve submitted jobs and grepped the files in /var/log/condor for âunimarkerâ but am not getting any results.

--
Gerard Weatherby | Application Architect
NMRbox | Department of Molecular Biology and Biophysics | UConn Health
263 Farmington Avenue, Farmington, CT 06030-6406
uchc.edu
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

Mailing List Archives

Public Access

Re: [HTCondor-users] Use of debug statement in machine configuration file