be in time or not to be in time ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hhm, found this in the log: Jun 28 03:58:37.000 [warn] Our clock is 1 minutes, 23 seconds behind the time published in the consensus network status document (2015-06-28 02:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings! NTP runs fine at this exit relay since months, and I found nothing in the log which would tell me that sth was wrong with the time. Any hints / explanations ? - -- Toralf pgp key: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 0076 E94E -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlWPuw0ACgkQxOrN3gB26U71+wD+PIH6JSVqR8SJ/43wwDZKNibH UdvUWwDG4eQQ5kn/3N4A/AydwluUvBMXXSy7fh+Zphg1dCUF+zq7jKmxzRYcAZ2A =bnzu -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I used to receive this message regularly from time to time on a KVM virtual machine running Debian 7 Wheezy (Tor exit relay). NTP process was working fine, no errors. I did manually: # service ntp stop # ntpdate 0.rhel.pool.ntp.org # service ntp start Are you using a virtual machine as well? If yes, the answer might be that the host is overwriting your guest (vm) clock. You can either disable hwclock, either disable ntp on guest (vm) operating system and rely on the clock of your host server. On 6/28/2015 12:14 PM, Toralf Förster wrote:
Hhm,
found this in the log:
Jun 28 03:58:37.000 [warn] Our clock is 1 minutes, 23 seconds behind the time published in the consensus network status document (2015-06-28 02:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
NTP runs fine at this exit relay since months, and I found nothing in the log which would tell me that sth was wrong with the time.
Any hints / explanations ?
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBCAAGBQJVkAZWAAoJEIN/pSyBJlsRzUkH/06LopXsYIV/mSMrow7e/F8I hm8S3SP6fTpvlFXaw2q3r4NDq/TO+8apinty18UYNT6de/PaKO3BnP9uQ/8EXjcp jK/T52W6y0T/PD/tq/yi9SLfZoL35msTeBrWc6z/+Qq0SYuJq69dt/YmJ1ml4Vah 8drG+AIDuBy8ttEKEOSvlrmgAnaqoC9+pDNLs5Sc8wpMudTseUAzL1myjrn4WBaT QXx+UJwH5pzniZT1N6foqYL9Tzggm5Y0GigyRgpuHRqt/s49iTOfIMo9VZtf3JxX v1tOhHs2d0Ne4TdFupZI4mTQaJpzlU/Vxls6e/VyDdrh7jQs7vKeV15GrLTlVFQ= =wbn8 -----END PGP SIGNATURE-----
On 06/28/2015 04:36 PM, s7r wrote:
Are you using a virtual machine as well? If yes, the answer might be that the host is overwriting your guest (vm) clock. You can either disable hwclock, either disable ntp on guest (vm) operating system and rely on the clock of your host server.
Nope, it is a dedicated server - and shouldn't ntp then log that it step'ed the clock ? Furthermore it was up and runnign for 8 days w/o any time problems and/or log AFICT. /me wonders, if the tor relay asked the authority - say at 3:58:30 - and got the answer at 04:00:00 - thereofre having a 90 sec delay ? -- Toralf pgp key: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 0076 E94E
participants (2)
-
s7r -
Toralf Förster