[tor-relays] Exit node with bad time.

[Bernard Tyers - ei8fdb]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Meant to send this to the list:

Yes, of course you're right - the timezone according to the /etc/timezone file is Europe/Zurich, which makes sense.

I had asked them to set it to GMT, but they said they could not (?). Their option was to change the timezone.

I didn't think of setting up ntpd to fix it. Much better solution.

thanks,
Bernard


On 2 Jul 2013, at 11:05, Steve Snyder wrote:

> That "CEST" you referred to is an offset that is applied to the actual time.  To check the actual (UTC) time, do this:
> 
> ntpdate -q 0.pool.ntp.org
> 
> If you are running in an OpenVZ container you will have to have your VPS vendor correct the system time on the node hosting your VPS.  Otherwise, you can keep the system time in your server accurate yourself by running the ntpd daemon.
> 
> 
> On Tuesday, July 2, 2013 4:31am, "Bernard Tyers - ei8fdb" <ei8fdb at ei8fdb.org> said:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Hi there,
>> 
>> 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
>> '86.59.21.38: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
>> 76.73.17.194: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 [1] 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?
>> 
>> thanks,
>> Bernard
>> 
>> 
>> 
>> [1] https://lists.torproject.org/pipermail/tor-relays/2011-November/001001.html
>> 
>> 
>> - --------------------------------------
>> Bernard / bluboxthief / ei8fdb
>> 
>> IO91XM / www.ei8fdb.org
>> 
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
>> Comment: GPGTools - http://gpgtools.org
>> 
>> iQEcBAEBAgAGBQJR0o/WAAoJENsz1IO7MIrr8SoIALW8W1+SawsVv6r2sLCEPetp
>> u05dGZ4E2vyuey5VIRfPsG1Lc2kPmE+dzY2jgHm2Q66htBqMXtv+WQ1P8TMBYyzj
>> ke/LkXOW2aE2NkyJ95navfnImJGWS+Ie4eyk+PnHL0d6RoRc9K2JKnQKTCPLRQvQ
>> kiFUkKWuHVn/aRzalrlKH7yFdoPosh5pdqqyRLQ4sDQ0dAye0u4GxfvMsrdCP8oO
>> ediSXiRaupSr24V+yK7ceZNUiEBcdNp6VudwJXQ+YH1uF4obSHeVWQFC7ZRpAbAI
>> VrqNVqBx7Xbij0wC83VR6ifz/AYJNoKlG56H72w/jg1hVwi7x58CIuLWBOm1bUM=
>> =2AY7
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>> 
> 
> 

- --------------------------------------
Bernard / bluboxthief / ei8fdb

IO91XM / www.ei8fdb.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJR0wFwAAoJENsz1IO7MIrriTcH/0qW7hhf/JXCUybU6axxi9zH
lj4vJUpGh8jglxcQsoIQbYOkTapdh0/wPSFyLdBbTxg6am3QDtwgUBjLB5O+T0FH
3o4aRVUSMimJwG7ZVuzKtEiL83ubO/h3YjyutAzxsY/CqFgaW4kgTIfWFCuD29RO
bnSbsZzIlo7aDjpit4i3u5rExKImP+G5DkX2EjrterS5CIZNQXmoI1MXWkUBZ+Li
vICrTckqPgiKN81nVQLwucm8ZrTKSgt9PwOyzF1xswsn/Zm3YYfw77z9Sr5p1gad
ZvxrhrODXLMImY+NEmJ627Zvx+Z4SC//EIIGrzR+KfDqqX9qkTUCRVo/aM543E4=
=g3zT
-----END PGP SIGNATURE-----