Re: [tor-relays] Tor stopped suddenly - clock/time issue

2019-11-06 Thread The Doctor [412/724/301/703/415/510]
‐‐‐ Original Message ‐‐‐
On Wednesday, November 6, 2019 2:04 AM, r1610091651  
wrote:

> Looks like there is no functioning hardware clock and so the time needs to be 
> received from ntp servers, which will take some time.
> 2 options:
> * add a real-time clock: 
> https://thepihut.com/blogs/raspberry-pi-tutorials/17209332-adding-a-real-time-clock-to-your-raspberry-pi
> * delay start of tor until time is setup

Third option: Get a USB GPS dongle and configure ntpd to use that as an 
authoritative time source.  That's what I did.

The Doctor [412/724/301/703/415/510]
PGP (new!): 4d7d 5c94  fa44 a235
WWW: https://drwho.virtadpt.net/
The old world is dying, and the new world struggles to be born. Now is the time 
of monsters.___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


[tor-relays] Tor stopped suddenly - clock/time issue

2019-11-06 Thread David Strappazon
Hi, while checking my (new)or not this is what i saw in notices.log

Nov 05 05:18:57.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 
unique clients.
Nov 05 10:44:17.000 [notice] Interrupt: we have stopped accepting new 
connections, and will shut down in 30 seconds. Interrupt again to exit now.
Nov 05 10:44:18.000 [notice] Delaying directory fetches: We are hibernating or 
shutting down.
Nov 05 10:44:47.000 [notice] Clean shutdown finished. Exiting.
Apr 11 18:28:44.000 [notice] Tor 0.4.1.6 opening log file.
Apr 11 18:28:44.103 [notice] Tor 0.4.1.6 running on Linux with Libevent 
2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.3.
Apr 11 18:28:44.103 [notice] Tor can't help you if you use it wrong! Learn how 
to be safe at https://www.torproject.org/download/download#warning
Apr 11 18:28:44.103 [notice] Read configuration file 
"/usr/share/tor/tor-service-defaults-torrc".
Apr 11 18:28:44.103 [notice] Read configuration file "/etc/tor/torrc".
Apr 11 18:28:44.125 [notice] Based on detected system memory, MaxMemInQueues is 
set to 694 MB. You can override this by setting MaxMemInQueues by hand.
Apr 11 18:28:44.128 [notice] Opening Socks listener on 127.0.0.1:9050
Apr 11 18:28:44.128 [notice] Opened Socks listener on 127.0.0.1:9050
Apr 11 18:28:44.128 [notice] Opening OR listener on 0.0.0.0:4433
Apr 11 18:28:44.128 [notice] Opened OR listener on 0.0.0.0:4433
Apr 11 18:28:44.128 [notice] Opening Extended OR listener on 127.0.0.1:0
Apr 11 18:28:44.128 [notice] Extended OR listener listening on port 40247.
Apr 11 18:28:44.128 [notice] Opened Extended OR listener on 127.0.0.1:40247
Apr 11 18:28:44.000 [notice] Bootstrapped 0% (starting): Starting
Apr 11 18:28:44.000 [warn] Received local state file with skewed time 
(/var/lib/tor/state): It seems that our clock is behind by 207 days, 17 hours, 
16 minutes, or that theirs is ahead. Tor requires an accurate clock to work: 
please check your time, timezone, and date settings.
Apr 11 18:28:44.000 [warn] Problem bootstrapping. Stuck at 0% (starting): 
Starting. (Clock skew -17946963 in local state file from /var/lib/tor/state; 
CLOCK_SKEW; count 1; recommendation warn; host ? at ?)
Nov 05 10:45:34.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Nov 05 10:45:35.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Nov 05 10:45:35.000 [notice] Configured to measure statistics. Look for the 
*-stats files that will first be written to the data directory in 24 hours from 
now.
Nov 05 10:45:43.000 [notice] Your Tor server's identity key fingerprint is 
'citizenfour B839503CA8F877D0263A38103DAF47EF302FBCF7'
Nov 05 10:45:43.000 [notice] Your Tor bridge's hashed identity key fingerprint 
is 'citizenfour 9D1CCBE7EEF99FCCA6F767838FA08B23DDFABB3A'
Nov 05 10:45:44.000 [warn] Our clock is 207 days, 16 hours, 31 minutes behind 
the time published in the consensus network status document (2019-11-05 
09:00:00 UTC).  Tor needs an accurate clock to work correctly. Please check 
your time and date settings!
Nov 05 10:45:44.000 [warn] Received ns flavor consensus with skewed time 
(CONSENSUS): It seems that our clock is behind by 207 days, 16 hours, 31 
minutes, or that theirs is ahead. Tor requires an accurate clock to work: 
please check your time, timezone, and date settings.
Nov 05 10:45:44.000 [warn] Problem bootstrapping. Stuck at 0% (starting): 
Starting. (Clock skew -17944276 in ns flavor consensus from CONSENSUS; 
CLOCK_SKEW; count 2; recommendation warn; host ? at ?)
Nov 05 10:45:45.000 [warn] Our clock is 207 days, 15 hours, 31 minutes behind 
the time published in the consensus network status document (2019-11-05 
08:00:00 UTC).  Tor needs an accurate clock to work correctly. Please check 
your time and date settings!
Nov 05 10:45:45.000 [warn] Received microdesc flavor consensus with skewed time 
(CONSENSUS): It seems that our clock is behind by 207 days, 15 hours, 31 
minutes, or that theirs is ahead. Tor requires an accurate clock to work: 
please check your time, timezone, and date settings.
Nov 05 10:45:45.000 [warn] Problem bootstrapping. Stuck at 0% (starting): 
Starting. (Clock skew -17940676 in microdesc flavor consensus from CONSENSUS; 
CLOCK_SKEW; count 3; recommendation warn; host ? at ?)
Nov 05 10:47:44.000 [notice] Starting with guard context "default"
Nov 05 10:47:44.000 [notice] Signaled readiness to systemd
Nov 05 10:47:44.000 [notice] Registered server transport 'obfs4' at '[::]:1234'
Nov 05 10:47:45.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Nov 05 10:47:45.000 [notice] Opening Socks listener on /run/tor/socks
Nov 05 10:47:45.000 [notice] Opened Socks listener on /run/tor/socks
Nov 05 10:47:45.000 [notice] Opening Control listener on /run/tor/control
Nov 05 10:47:45.000 [notice] Opened Control listener on /run/tor/control
Nov 05 10:47:45.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Nov 05 10:47:47.000 [notice] Bootstrapped 14% (handshake): Handshaking with a 
relay
Nov 0