Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Need help debugging HIBERNATE/ROOSTER
- Date: Wed, 19 Nov 2025 16:00:21 +0100
- From: Steffen Grunewald <steffen.grunewald@xxxxxxxxxx>
- Subject: Re: [HTCondor-users] Need help debugging HIBERNATE/ROOSTER
On Tue, 2025-11-18 at 13:11:24 -0600, HTCondor Users Mailinglist wrote:
> > What makes "DaemonStartTime" break the expression above, once evaluation gets
> > that far?
>
> It might be coincidence, given the size of our manual, but
> `DaemonStartTime` is _not_ listed as a machine ClassAd* attibute. The
> manual** specifies that HIBERNATE is evaluated in the context of "each slot
> on the machine", which I presume to mean a machine ad.
DaemonStartTime, among other candidates for telling me how long this system might
have been powered on, is returned by `condor_status -l | grep Time`, and it looked
tempting. 'time()-DaemonStartTime' returned useful values on all slots/machines
I could reach, so indeed I didn't suspect it'd be something taken out of thin air.
> *: https://htcondor.readthedocs.io/en/latest/classad-attributes/machine-classad-attributes.html
> **: https://htcondor.readthedocs.io/en/latest/admin-manual/configuration-macros.html#HIBERNATE
>
> So I expect that if you actually `debug()` that expression,
> `DaemonStartTime` will be undefined.
It may indeed be - in that special situation only.
Whatever the cause, I've found a workaround and added a line or two to my notes.
So: thanks,
Steffen