-----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