-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I just looking on the logs and see:
==cut== Sep 02 21:03:54.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:443. It seems that our clock is behind by 1 hours, 24 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:06:04.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is ahead by 1 hours, 4 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:06:08.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is ahead by 3 hours, 35 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:06:58.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is behind by 5 hours, 58 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:08:53.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is behind by 1 hours, 54 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:10:49.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is behind by 5 hours, 55 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:11:51.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:8443. It seems that our clock is ahead by 1 hours, 26 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:11:52.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:449. It seems that our clock is ahead by 1 hours, 19 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings. ==cut==
Should I worry about it? Logs seems to little strange and looks that other servers provide it's local time without any timezone.
[root@fido tor]# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== +x.x.x.x .PPS. 1 u 11 64 377 15.026 2.142 3.279 +x.x.x.x .PPS. 1 u 26 64 377 8.315 2.734 4.281 +x.x.x.x .PPS. 1 u 2 64 377 6.511 0.973 3.214 *x.x.x.x .PPS. 1 u 60 64 377 6.395 2.162 1.869 oGPS_NMEA(0) .GPS. 0 l 15 16 377 0.000 0.014 0.009
And server is a part of ntppool - valid.
Regards,
- -- Marcin Gondek / Drixter http://fido.e-utp.net/ AS56662
Hi,
On 02 Sep 2014, at 21:19, Marcin Gondek drixter@e-utp.net wrote:
I just looking on the logs and see:
==cut== Sep 02 21:03:54.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:443. It seems that our clock is behind by 1 hours, 24 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings.
Should I worry about it? Logs seems to little strange and looks that other servers provide it's local time without any timezone.
These are info-level logs. You should not worry about them unless you're trying to chase an issue you've observed otherwise.
Cheers Sebastian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I just wondering, it is a bug?
Regards,
- -- Marcin Gondek / Drixter http://fido.e-utp.net/ AS56662
- -----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of Sebastian Hahn Sent: Tuesday, September 02, 2014 10:18 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Time information
Hi,
On 02 Sep 2014, at 21:19, Marcin Gondek drixter@e-utp.net wrote:
I just looking on the logs and see:
==cut== Sep 02 21:03:54.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:443. It seems that our clock is behind by 1 hours, 24 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings.
Should I worry about it? Logs seems to little strange and looks that other servers provide it's local time without any timezone.
These are info-level logs. You should not worry about them unless you're trying to chase an issue you've observed otherwise.
Cheers Sebastian
On Wed, Sep 03, 2014 at 05:19:13AM +0000, Marcin Gondek wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I just wondering, it is a bug?
Regards,
AFAIK, there is no bug. I used to see this message when I was behind a router with wrong UTC summer/winter time configuration. Now I don't see them anymore. Are you sure your time zone settings are properly configured?
Regards,
Hi,
My zone it's correct, when I will have a wrong time the NTP Pool will "out" me from the pool.
http://www.pool.ntp.org/user/drixter
The same machine, where relay is running.
[drixter@fido ~]$ ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== +smtp.certum.pl .PPS. 1 u 61 64 377 14.443 2.168 4.001 +tempus1.gum.gov .PPS. 1 u 45 64 377 6.704 1.905 3.127 +tempus2.gum.gov .PPS. 1 u 12 64 367 7.376 2.228 4.053 *ntp.coi.pw.edu. .OCXO. 1 u 40 64 377 6.869 2.267 1.975 oGPS_NMEA(0) .GPS. 0 l 5 16 377 0.000 0.010 0.026 [drixter@fido ~]$ date Thu Sep 4 21:49:59 CEST 2014 [drixter@fido ~]$
Regards,
On Tue, Sep 02, 2014 at 07:19:02PM +0000, Marcin Gondek wrote:
Sep 02 21:11:52.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:449. It seems that our clock is ahead by 1 hours, 19 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings.
Should I worry about it? Logs seems to little strange and looks that other servers provide it's local time without any timezone.
It isn't a bug, but it is not great that some Tor relays have the wrong time. But so long as they aren't *too* wrong, it isn't the end of the world. I just counted them up, and I think there are about 30 relays with wrong clocks, out of the 6000 or so total. That's pretty good.
I think those relays are probably seeing complaints in their logs, since while you see those at info-level because they're not directory authorities, when you notice that a directory authority disagrees with your clock, it's logged at warn-level severity.
I wonder how to get them to notice more consistently?
--Roger
On Thu, Sep 4, 2014 at 7:04 PM, Roger Dingledine arma@mit.edu wrote:
I wonder how to get them to notice more consistently?
Simple, either mail their contact (if any) and they fix it, or blacklist their fingerprints. There is no reason any relay should not be able to sync time.
On 2014-09-05 03:43, grarpamp wrote:
I wonder how to get them to notice more consistently?
Simple, either mail their contact (if any) and they fix it, or blacklist their fingerprints. There is no reason any relay should not be able to sync time.
Other possibilities: - extend the Tor Weather service to detect this and send mail - assign a flag (i.e. "BadClock") when the clock is way out of sync
Using the contact info wouldn't work for me personally, since I didn't put a machine-readable email address in there.
Best regards, Alexander
Hi,
+1 from me for the flag
If the time issues really make a problems in tor network.
Regards,
tor-relays@lists.torproject.org
-
Alexander Dietrich -
grarpamp -
L. Blissett -
Marcin Gondek -
Roger Dingledine -
Sebastian Hahn