Re: [tor-relays] be in time or not to be in time ?

[s7r <s7r@xxxxxxxxxx>]

-----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@xxxxxxxxxxxxxxxxxxxx 
> 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-----
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays