On Tue, Oct 23, 2018 at 01:13:53AM -0700, Keifer Bly wrote:
Tonight when I went to check it, tor metrics said it had said it was offline for the last 11 hours.
Two thoughts, based on your log:
Oct 19 23:33:16.972 [notice] Opening OR listener on 0.0.0.0:9002 Oct 19 23:35:05.000 [notice] Registered server transport 'obfs4' at '[::]:9002'
It looks like your ORPort is 9002, and also your ServerTransportListenAddr is trying to use 9002? That could result in weirdness.
Oct 21 17:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 17:59 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB. Oct 23 00:47:29.000 [warn] Your system clock just jumped 112349 seconds forward; assuming established circuits no longer work.
Something weird happened here -- it's like the process went to sleep for 31 hours. This is the sort of thing that happens when you close your laptop and then open it 31 hours later.
There are not many Windows relays (or bridges), so it could be all sorts of things -- a libevent bug? A thing that Microsoft chose to implement in a surprising way that's different from every other platform? An antivirus app that tried to hook the Tor process and ended up wedging it for 31 hours? A clock that jumped backwards by 31 hours?
I wonder if it's https://trac.torproject.org/26360
--Roger