Re: [HTCondor-users] token_key with remote accesspoint

["Weatherby,Gerard" <gweatherby@xxxxxxxx>]

Within about 1/1000 of a second – they’re all using the same timeserver:

gweatherby@accesspoint:~$ ntpdate -q time.bioscience-ct.net

server 192.92.158.10, stratum 3, offset -0.000102, delay 0.02637

21 Jul 15:08:29 ntpdate[246527]: adjust time server 192.92.158.10 offset -0.000102 sec

gweatherby@test-condor1:~$ ntpdate -q time.bioscience-ct.net

server 192.92.158.10, stratum 3, offset 0.000063, delay 0.02649

21 Jul 15:07:10 ntpdate[136910]: adjust time server 192.92.158.10 offset 0.000063 sec

 

gweatherby@condorcentralmanager:~$ ntpdate -q time.bioscience-ct.net

server 192.92.158.10, stratum 3, offset -0.000023, delay 0.02655

21 Jul 15:09:18 ntpdate[394335]: adjust time server 192.92.158.10 offset -0.000023 sec

 

From: Todd L Miller <tlmiller@xxxxxxxxxxx>
Date: Friday, July 21, 2023 at 2:44 PM
To: Weatherby,Gerard <gweatherby@xxxxxxxx>
Cc: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] token_key with remote accesspoint

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

> Now here’s the bizzaro thing. If I replace the time limited token with
> an unrestricted one:

        Check to make sure all three machines have synchronized clocks
(and/or are in the same timezone)?

- ToddM