[tor-relays] new warning with Tor 0.3.4.0-alpha-dev (git-efc105716283bbdf)

[Toralf Förster]

On 02/19/2018 07:32 PM, Toralf Förster wrote:
> This happenes here now with that version usually once a day.
> 
> Feb 19 18:59:00.000 [warn] Our clock is 1 minutes, 1 seconds behind the time published in the consensus network status document (2018-02-19 18:00:00 UTC).  Tor needs an accurate clock to work correctly. Please check your time and date settings!
> Feb 19 18:59:00.000 [warn] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 1 minutes, 1 seconds, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
FWIW I do have a watchdog scripted which sends me an email if this happens.
That watchdog contains these sequence :

      echo "date -u"
      date -u
      echo
      
      echo "cat </dev/tcp/time.nist.gov/13"
      cat </dev/tcp/time.nist.gov/13
      echo
      
      echo "ntpdate -q 2.de.pool.ntp.org"
      ntpdate -q 2.de.pool.ntp.org
      echo


so I'm convinved that this output today :



date -u
Tue Feb 27 14:59:00 UTC 2018

cat </dev/tcp/time.nist.gov/13

ntpdate -q 2.de.pool.ntp.org
server 2a01:4f8:110:30e1::9, stratum 2, offset 0.001730, delay 0.02591
server 2a01:4f8:202:3328::c10c, stratum 2, offset 0.000137, delay 0.02602
server 2a03:4000:1c:c8::1, stratum 2, offset -0.000501, delay 0.02858
server 2001:638:504:2000::32, stratum 2, offset 0.003275, delay 0.04170
server 46.4.106.197, stratum 2, offset 0.000111, delay 0.02597
server 78.46.189.152, stratum 3, offset 0.000517, delay 0.02603
server 195.50.171.101, stratum 2, offset 0.000814, delay 0.03128
server 62.116.162.126, stratum 2, offset -0.000336, delay 0.03647
27 Feb 15:59:10 ntpdate[3213]: adjust time server 2a01:4f8:110:30e1::9 offset 0.001730 sec


Feb 27 15:59:00.000 [warn] Our clock is 1 minutes, 1 seconds behind the time published in the consensus network status document (2018-02-27 15:00:00 UTC).  Tor needs an accurate clock to work correctly. Please check your time and date settings!
Feb 27 15:59:00.000 [warn] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 1 minutes, 1 seconds, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.



indicates that the remote side is wrong.

-- 
Toralf
PGP C4EACDDE 0076E94E

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20180227/c0f6f63f/attachment.sig>