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

I noticed that the system is running Windows10? If this is the situation then you might want to downgrade the server to anything. Not knowing the ISP service I cannot say for certain, but, ATT and most of the cable companies have signed agreements with NSA and DHS to interrupt services to the dark web, or at least report and track access. MS Win10 is actually copying everything back to the MS servers furthering Bill Gates dream of having "Every Computer in the World on a single peer to peer network". See if there is a "Router" log that might identify an external access problem or "Denial of access" issue. Good Luck!!!

On Tue, Oct 23, 2018 at 1:47 PM Keifer Bly <keifer.bly@xxxxxxxxx> wrote:

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

Good point out, but that seems very strange as it is a desktop computer my relay runs on, which is set (via the Windows sleep settings) to not turn fully off and only put the screen to sleep. The relay was online for a few days without interruption beforehand. I use Avast as my antivirus software, which notifies me if it detects something as a virus which it has not done. Strange. I am running the newest version of both tor and obfs4, and I keep Windows up to date as well. My web browser was playing a video the whole time which did not get interrupted at all, so it doesn't look like my internet stopped..?

Thanks for the thoughts and help. Wonder what could have caused it out of the blue....

> you should've
redact Tor log to remove external IP address and unhashed fingerprint as
this mailing list is public and can be read by anyone.

Ahhh... darn that's a good point. The good news is I have a dynamic ip (from my ISP) which shouldn't be too difficult to change if needed.

On Tue, Oct 23, 2018 at 1:34 AM Roger Dingledine <arma@xxxxxxx> wrote:
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

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays