Opened 6 years ago

Last modified 2 years ago

#10566 new defect

tor relay hangs for 20 seconds periodically if domain from Address can not be resolved

Reported by: erchewin Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Normal Keywords: tor-relay nonblocking dns
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

tor version: 0.2.4.20-1
Debian sid i686

This problem started few hours ago. I checked many sources of problem. I even thought NSA delays my connections with Tor netwerk to fingerprint me :) Then I checked another tor instance, from tor browser, where no Address is specified, it worked fine.

The reason occurred to be in Down DNS server. Domain I specified for Address, was not resolved. I commented out Address, now Tor works fine!

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-final

We should use nonblocking lookups for this kind of thing when Tor is running, and only do a blocking lookup for our Address at startup. That's comparatively easy when we're built against Libevent 2.0, where evutil_getaddrinfo_async() should let us look up Address nonblockingly without too much trouble.

comment:2 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:3 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:4 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:5 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 2 years ago by nickm

Keywords: tor-relay nonblocking dns added
Severity: Normal
Note: See TracTickets for help on using tickets.