[tor-relays] Exit node with bad time.
Bernard Tyers - ei8fdb
ei8fdb at ei8fdb.org
Tue Jul 2 08:31:17 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
I am running an exit node on a VPS. For some reason (I've opened a support ticket) a) my systems clock is off by 2 hours (even though its hosted in CEST land) and b) I cannot change it, even though I am root.
As a result, I am getting recurring skewed time errors as below:
Accounting (awake) Time to reset: 29:12:02:58
21 GB / 1 PB 22 GB / 1 PB
Events (TOR/ARM NOTICE - ERR):
│ 12:25:39 [WARN] Received directory with skewed time (server '188.8.131.52:80'): It seems that our clock is ahead by 2 hours, 3 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
│ 12:25:03 [WARN] Received NETINFO cell with skewed time from server at 184.108.40.206:9090. It seems that our clock is ahead by 2 hours, 3 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings.
I haven't found any mention in the archives of this (except  which is NOT the same, just mentions wrong time), if it results in issues to the network overall.
Until I can get it resolved (today hopefully) is there any negative affects on the network of having a node with bad time?
Bernard / bluboxthief / ei8fdb
IO91XM / www.ei8fdb.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
-----END PGP SIGNATURE-----
More information about the tor-relays