Re: [HTCondor-users] custom ClassAd again (how to debug crondor)?

["John (TJ) Knoeller" <johnkn@xxxxxxxxxxx>]

use
   condor_status -direct <machine> -long

to see the current startd ad without waiting for it to update the collector.

To see if your startd cron script is running. look in the log file for messages that begin with "CronJob:". 
if you set D_FULLDEBUG, you should see messages for success as well as failure.

One of the D_FULLDEBUG messages will contain "<name>: %d lines in Queue" whenever your script has sent back data for startd cron to read.
Another message is  "Adding '<name>' to the 'extra' ClassAd list" or "Replacing ClassAd for '<name>' when the startd cron ad is written into the startd.

There is no way to have HTCondor echo the actual contents of your startd cron ad to the log file. but if your job returns something that won't parse, you should expect to see error messages in the log.

-tj

On 6/2/2015 2:04 PM, Dimitri Maziuk wrote:

On 06/02/2015 01:30 PM, John (TJ) Knoeller wrote:

Sorry, I misread what you had said before.  the real question is does
condor_config_val -config show that it read the output of your script?

No, it does not show the output of my script.

you should NOT expect to see attributes set by crondor (startd cron?) in
the output of condor_config_val -dump.

Well, OK, how can I check them then?

_______________________________________________
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/