[tor-bugs] #20423 [Core Tor/Tor]: Clock jumps on FreeBSD relay
Tor Bug Tracker & Wiki
blackhole at torproject.org
Fri Nov 11 06:10:37 UTC 2016
#20423: Clock jumps on FreeBSD relay
--------------------------------+------------------------------------
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 Felixix):
The mistery seems solved! After setting `Address my.ext.i.p` the hourly
warnings and the stalling is gone again. What one would do if guessing
becomes necessary (dynamic ip) ?
Two relays are configured newly and both work fine. I am confident to
switch all relays to 0.2.8.9 now.
And tell me if I shall test a modified ip guessing sometimes. My setup
(jail) seems sensitive and reproducible for it.
Thanks to everybody
----
0.2.8.9 with `Address my.ext.i.p`
'''torrc good'''
Address my.ext.i.p
ORPort my.ext.i.p:443 NoListen
ORPort my.loc.i.p:1234 NoAdvertise
DirPort my.ext.i.p:80 NoListen
DirPort my.loc.i.p:5678 NoAdvertise
'''top''' tor process shows no stalling.
----
0.2.8.9 without `Address my.ext.i.p`
'''torrc bad'''
#Address my.ext.i.p
ORPort my.ext.i.p:443 NoListen
ORPort my.loc.i.p:1234 NoAdvertise
DirPort my.ext.i.p:80 NoListen
DirPort my.loc.i.p:5678 NoAdvertise
'''log bad'''
...
Nov 10 07:30:47.410 [notice] Tor v0.2.8.9 running on FreeBSD with Libevent
2.0.22-stable, OpenSSL LibreSSL 2.4.3 and Zlib 1.2.8.
...
Nov 10 07:30:47.425 [notice] Opening OR listener on my.loc.i.p:1234
Nov 10 07:30:47.426 [notice] Opening Directory listener on my.loc.i.p:5678
...
Nov 10 07:36:43.000 [notice] Guessed our IP address as my.ext.i.p
...
Nov 10 09:36:27.000 [warn] Your system clock just jumped 321 seconds
forward; assuming established circuits no longer work.
Nov 10 09:36:28.000 [warn] assign_to_cpuworker failed. Ignoring.
in total 168 times
Nov 10 09:36:30.000 [warn] assign_to_cpuworker failed. Ignoring.
...
Nov 10 10:36:30.000 [warn] Your system clock just jumped 325 seconds
forward; assuming established circuits no longer work.
Nov 10 10:36:31.000 [warn] assign_to_cpuworker failed. Ignoring.
in total 171 times
Nov 10 10:36:33.000 [warn] assign_to_cpuworker failed. Ignoring.
...
Nov 10 11:36:30.000 [warn] Your system clock just jumped 325 seconds
forward; assuming established circuits no longer work.
Nov 10 11:36:31.000 [warn] assign_to_cpuworker failed. Ignoring.
in total 164 times
Nov 10 11:36:33.000 [warn] assign_to_cpuworker failed. Ignoring.
'''top bad''' tor process
2016-11-10_11-40-00 25.98% tor
2016-11-10_11-39-00 17.97% tor
2016-11-10_11-38-00 11.96% tor
2016-11-10_11-37-00 13.96% tor
2016-11-10_11-36-00 3.96% tor
2016-11-10_11-35-00 1.95% tor
2016-11-10_11-34-00 3.96% tor
2016-11-10_11-33-00 3.96% tor
2016-11-10_11-32-00 3.96% tor
2016-11-10_11-31-00 19.97% tor
2016-11-10_11-30-00 19.97% tor
2016-11-10_11-29-00 17.97% tor
2016-11-10_11-28-00 21.97% tor
2016-11-10_11-27-00 25.98% tor
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20423#comment:27>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list