> On 28 Feb 2018, at 04:18, Toralf Förster <[email protected]> wrote: > > 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 > … > 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.
The message is accurate, although it might be 1 second off: "It seems that our clock is behind by 1 minutes, 1 seconds, or that theirs is ahead" It is possible that an authority is ahead by 1 minute + download time. Or that there is a bug in the relevant Tor code. Here are the questions I'd like to answer before opening a ticket: Which authority did your Tor fetch the consensus from? Is that authority's clock wrong? Does this error happen often on your relay? T _______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
