[tor-relays] Tor bridge on Windows 10 going down for a reason I cannot detect?

Tue Oct 23 08:13:53 UTC 2018

Hello all, for some reason my tor bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032ECF14E5B9E9A is randomly removed from the network. Tonight when I went to check it, tor metrics said it had said it was offline for the last 11 hours. This is very strange as I had not closed the tor software and my internet had not disconnected at all. Below is the tor log file, it is tor 0.3.4.8 on Windows 10, any thoughts would be great. Thanks.

Oct 19 23:33:16.910 [notice] Tor 0.3.4.8 (git-da95b91355248ad8) running on Windows 8 with Libevent 2.1.8-stable, OpenSSL 1.0.2p, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Oct 19 23:33:16.910 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Oct 19 23:33:16.957 [notice] Read configuration file "C:\Users\keife\AppData\Roaming\tor\torrc.txt".
Oct 19 23:33:16.972 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\keife\AppData\Roaming\tor\<default>. Is this what you wanted?
Oct 19 23:33:16.972 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\keife\AppData\Roaming\tor\<default>. Is this what you wanted?
Oct 19 23:33:16.972 [notice] Based on detected system memory, MaxMemInQueues is set to 2048 MB. You can override this by setting MaxMemInQueues by hand.
Oct 19 23:33:16.972 [notice] Scheduler type KISTLite has been enabled.
Oct 19 23:33:16.972 [notice] Opening OR listener on 0.0.0.0:9002
Oct 19 23:33:16.972 [notice] Opening Extended OR listener on 127.0.0.1:0
Oct 19 23:33:16.972 [notice] Extended OR listener listening on port 56515.
Oct 19 23:33:57.000 [notice] Parsing GEOIP IPv4 file C:\Users\keife\AppData\Roaming\tor\geoip.
Oct 19 23:33:57.000 [notice] Parsing GEOIP IPv6 file C:\Users\keife\AppData\Roaming\tor\geoip6.
Oct 19 23:33:57.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.
Oct 19 23:33:58.000 [notice] Your Tor server's identity key fingerprint is 'torland 8C6C18F8D95918F9DC90A09827DAD285064F8872'
Oct 19 23:33:58.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'torland 148BD64BED9F2C27637D986DE032ECF14E5B9E9A'
Oct 19 23:33:58.000 [notice] Bootstrapped 0%: Starting
Oct 19 23:35:03.000 [notice] Starting with guard context "default"
Oct 19 23:35:03.000 [notice] Bootstrapped 5%: Connecting to directory server
Oct 19 23:35:05.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Oct 19 23:35:05.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection
Oct 19 23:35:05.000 [notice] Registered server transport 'obfs4' at '[::]:9002'
Oct 19 23:35:05.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus
Oct 19 23:35:06.000 [notice] Bootstrapped 50%: Loading relay descriptors
Oct 19 23:35:06.000 [notice] Guessed our IP address as 174.87.240.59 (source: 136.243.176.148).
Oct 19 23:35:15.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Oct 19 23:35:15.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Oct 19 23:35:18.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Oct 19 23:35:18.000 [notice] Bootstrapped 100%: Done
Oct 19 23:35:18.000 [notice] Now checking whether ORPort 174.87.240.59:9002 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Oct 19 23:35:21.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Oct 19 23:36:44.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 1000 buildtimes.
Oct 19 23:36:45.000 [notice] Performing bandwidth self-test...done.
Oct 20 05:35:00.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 0 circuits open. I've sent 3.08 MB and received 14.49 MB.
Oct 20 05:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
Oct 20 11:35:00.000 [notice] Heartbeat: Tor's uptime is 11:59 hours, with 1 circuits open. I've sent 4.38 MB and received 19.35 MB.
Oct 20 11:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
Oct 20 17:35:00.000 [notice] Heartbeat: Tor's uptime is 17:59 hours, with 0 circuits open. I've sent 5.74 MB and received 23.84 MB.
Oct 20 17:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
Oct 20 20:49:17.000 [notice] Channel padding timeout scheduled 180307ms in the past.
Oct 20 23:35:00.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 1 circuits open. I've sent 7.19 MB and received 28.20 MB.
Oct 20 23:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
Oct 21 05:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 5:59 hours, with 0 circuits open. I've sent 8.77 MB and received 34.02 MB.
Oct 21 05:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
Oct 21 11:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 11:59 hours, with 0 circuits open. I've sent 10.16 MB and received 38.10 MB.
Oct 21 11:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
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 [notice] Diagnostic for issue 8387: Found 1 one-hop circuits more than 1800 seconds old! Logging 1...
Oct 23 00:47:29.000 [notice]   #0 created at 2018-10-21 17:34:12. open, General-purpose client. Not marked for close. Package window: 1000. usable for new conns. Dirty since 2018-10-21 17:34:13 (112396 seconds vs 600-second cutoff).
Oct 23 00:47:29.000 [notice] It has been 112368 seconds since I last called circuit_expire_old_circuits_clientside().
Oct 23 00:47:29.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
Oct 23 00:47:29.000 [warn] Your system clock just jumped 112349 seconds forward; assuming established circuits no longer work.
Oct 23 00:47:31.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent usable consensus.
Oct 23 00:48:29.000 [notice] Heartbeat: Tor's uptime is 1 day 18:00 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB.
Oct 23 00:48:29.000 [notice] Diagnostic for issue 8387: Found 1 one-hop circuits more than 1800 seconds old! Logging 1...
Oct 23 00:48:29.000 [notice]   #0 created at 2018-10-21 17:34:12. open, General-purpose client. Marked for close. Package window: 1000. Not usable for new conns. Dirty since 2018-10-21 17:24:13 (113056 seconds vs 600-second cutoff).
Oct 23 00:48:29.000 [notice] It has been 59 seconds since I last called circuit_expire_old_circuits_clientside().
Oct 23 00:48:29.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
Oct 23 00:48:32.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
Oct 23 00:48:35.000 [notice] We now have enough directory information to build circuits.
Oct 23 00:48:36.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Oct 23 00:48:36.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20181023/55fc4d87/attachment.html>