Opened 6 years ago

Last modified 17 months ago

#7966 new defect

When Tor hibernates it should eventually resume, but on win7 it reports "address already in use".

Reported by: ioneyes Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.3.25
Severity: Normal Keywords: tor-relay hibernation win32 needs-insight
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I have a Tor node that is set to hibernate after an amount of data has been served.

I would normally expect the node to resume normal activity when its hibernation time is over.

Unfortunately on windows7 the Tor node reports the following upon resume from Tor hibernation.

"""Could not bind to 0.0.0.0:9443: Address already in use [WSAEADDRINUSE ]. Is Tor already running?"""

Child Tickets

Change History (5)

comment:1 Changed 6 years ago by nickm

Keywords: tor-relay hibernation added
Milestone: Tor: unspecified

Does this happen every time it comes out of hibernation? My guess here would be that some other process bound port 9433 while Tor was hibernating. Were you also running some other program that binds ports and might have bound this one?

comment:2 Changed 6 years ago by arma

Isn't Windows the system where you can bind a port that's already bound, and it basically means that you're in line to receive connections once the earlier one closes?

comment:3 Changed 6 years ago by ioneyes

Hi,

This occurs every time Tor resumes from hibernate on my 2 windows 7 boxes i'm afraid.
I have seen this behavior for some time now. Seeing it on 2 boxes over a period of time prompted me to open the case.

comment:4 Changed 6 years ago by ioneyes

There are no other processes running on the machine that use that port.
I have a tool to report 'ports in use', which I used to verify this.

comment:5 Changed 17 months ago by nickm

Keywords: win32 needs-insight added
Severity: Normal
Note: See TracTickets for help on using tickets.