[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20423 [Core Tor/Tor]: Clock jumps on FreeBSD relay due to hostname lookup timeouts (was: Clock jumps on FreeBSD relay)
#20423: Clock jumps on FreeBSD relay due to hostname lookup timeouts
--------------------------------+------------------------------------
Reporter: Felixix | Owner:
Type: defect | Status: new
Priority: High | Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor | Version: Tor: 0.2.8.9
Severity: Normal | Resolution:
Keywords: regression freebsd | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------+------------------------------------
Comment (by teor):
Ok, so #20610 deals with the excessive logging part of this issue, #19974
deals with the monotonic time part of this issue.
I suspect that `[warn] assign_to_cpuworker failed. Ignoring.` is a symptom
of the host name lookup timeout. So I've retitled this issue to focus on
the hostname lookup timeout.
We could improve this issue by avoiding calling getaddrinfo() or
gethostbyname() so often (although it's only being called once per hour,
which is probably the right frequency), or by somehow putting a lower
timeout on it, or by calling it asynchronously.
Alternately, we could log a message when tor_addr_lookup() takes more than
N seconds, encouraging relay operators to set 'Address', modify /etc/hosts
and /etc/hostname, or use IP addresses rather than hostnames in their
config.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20423#comment:28>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs