Hi again Tom Just an FYI that I have tested a startd classad hook that evaluates the result from an nslookup command and sets a classad called dns_ok to true or false. Kind of kludgy as nslookup (on windows) very cleverly does not return an error code when there is an error. Â\_(ã)_/Â So the batch file needs to parse the output of the command. Anyway, it works, so thanks for that. I wonât be deploying it yet as itâs a backup for our Networks or DNS or Security Teams sorting out the actual real problem, i.e. apparent vlan or firewall or dns servers causing the issue. Cheers Greg From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Greg.Hitchen@xxxxxxxx Thanks Tom, Iâll look into this as well. Something dynamic would be better, as the current kludge will rely on a static list of machines manually scraped from the userâs failed job stdout log files. Cheers Greg From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of tpdownes@xxxxxxxxx Greg: What you want is a startd classad hook that periodically queries this particular hostname and publishes a boolean attribute which evaluates to True if the resolution succeeds and False otherwise. Then direct the user to express this as
a job requirement. Hooks can be used for other purposes, but here the idea is for it to define a measure of its own health and express it as an attribute. Honestly, if DNS is flaky you might simply consider making this attribute a requirement for all jobs
via APPEND_REQUIREMENTS. Tom On Wed, May 12, 2021 at 7:32 PM Hitchen, Greg (IM&T, Kensington WA) <Greg.Hitchen@xxxxxxxx> wrote:
|