Opened 3 years ago

Closed 3 years ago

#21807 closed defect (worksforme)

tor.exe hangs on “[notice] Opening OR listener on 0.0.0.0:9001”

Reported by: rorosaurus Owned by:
Priority: Medium Milestone:
Component: - Select a component Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Last night I encountered this issue and haven't been able to find a solution from the wiki, stackexchange, or IRC.

I'm trying to run a non-exit relay on Windows Server 2012. tor.exe bootstrapped to 100% last night, but I hadn't configured logging (which I needed to confirm the 20 minute port checker thing), so I closed it and relaunched. Now it doesn't get past the opening OR listener line.

I've added 9001 to my firewall exceptions and endpoints for my Azure VM, and confirmed this port is accessible using http://ismyportopen.com/.

I've restarted, deleted the Data folder and the contents of Roaming and tried to start from scratch, but it appears like some information is retained. I didn't see it regenerate keys and such. Is there a way to reset tor entirely to confirm whether I somehow corrupted its state?


tor.exe output


Mar 23 12:55:21.671 [notice] Tor 0.2.9.10 (git-1f6c8eda0073f464) running on Wind
ows 8 [server] with Libevent 2.0.22-stable, OpenSSL 1.0.2k and Zlib 1.2.8.
Mar 23 12:55:21.702 [notice] Tor can't help you if you use it wrong! Learn how t
o be safe at https://www.torproject.org/download/download#warning
Mar 23 12:55:21.796 [notice] Read configuration file "C:\Users\rory\AppData\Roam
ing\tor\torrc".
Mar 23 12:55:21.796 [warn] Path for GeoIPFile (<default>) is relative and will r
esolve to C:\Users\rory\<default>. Is this what you wanted?
Mar 23 12:55:21.796 [warn] Path for GeoIPv6File (<default>) is relative and will

resolve to C:\Users\rory\<default>. Is this what you wanted?

Mar 23 12:55:21.796 [notice] Your ContactInfo config option is not set. Please c
onsider setting it, so we can contact you if your server is misconfigured or som
ething else goes wrong.
Mar 23 12:55:21.812 [notice] Opening OR listener on 0.0.0.0:9001


below is my torrc file


SOCKSPort 0
Log notice file C:\tor-win32-0.2.9.10\log\tor\notices.log
ORPort 9001
Nickname ignorethis
AccountingMax 45 GBytes
AccountingStart month 1 00:00
ExitPolicy reject *:* # no exits allowed

Child Tickets

Change History (1)

comment:1 Changed 3 years ago by rorosaurus

Resolution: worksforme
Status: newclosed

Nothing to see here. Just a silly human.

After specifying the log file location, all [notice] logs go there instead of to my command window output. :) After checking the logs (seriously, how did I not think to do that??) I see that the relay is operating fine.

Resolving as worksforme.

Note: See TracTickets for help on using tickets.