Opened 18 months ago

Closed 9 months ago

#25136 closed defect (fixed)

"system clock jump" warnings still persist

Reported by: bundesgebaermutter Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.3.2.9
Severity: Normal Keywords: clock, jumped, 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

This is an addition to #25052 as it was directly closed before I could reply.

I have changed my relay settings as recommended and disabled the "DirCache", set an "Address" and removed the (in any case temporary) cpu pinning. At least it helped to reduce the "jump clock" warnings to one every one or two hours. But they are not gone.

Feb  2 06:08:11 <daemon.notice> Tor[1941]:  Heartbeat: Tor's uptime is 1 day 11:27 hours, with 0 circuits open. I've sent 13.59 MB and received 26.91 MB.
Feb  2 06:08:11 <daemon.notice> Tor[1941]:  Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
Feb  2 06:08:11 <daemon.notice> Tor[1941]:  Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 20 v4 connections; and received 11 v1 connections, 22 v2 connections, 0 v3 connections, and 131 v4 connections.
Feb  2 12:08:11 <daemon.notice> Tor[1941]:  Heartbeat: Tor's uptime is 1 day 17:27 hours, with 0 circuits open. I've sent 13.59 MB and received 26.91 MB.
Feb  2 12:08:11 <daemon.notice> Tor[1941]:  Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
Feb  2 12:08:11 <daemon.notice> Tor[1941]:  Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 20 v4 connections; and received 11 v1 connections, 22 v2 connections, 0 v3 connections, and 131 v4 connections.
Feb  2 12:11:51 <daemon.notice> Tor[1941]:  Your IP address seems to have changed to 178.1.226.79 (METHOD=RESOLVED HOSTNAME=bundesgebaermutter.ddnss.eu). Updating.
Feb  2 12:11:51 <daemon.notice> Tor[1941]:  Our IP Address has changed from 178.1.228.74 to 178.1.226.79; rebuilding descriptor (source: METHOD=RESOLVED HOSTNAME=bundesgebaermutter.ddnss.eu).
Feb  2 12:11:57 <daemon.notice> Tor[1941]:  Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Feb  2 12:11:58 <daemon.notice> Tor[1941]:  Tor has successfully opened a circuit. Looks like client functionality is working.
Feb  2 12:11:58 <daemon.notice> Tor[1941]:  Tor has successfully opened a circuit. Looks like client functionality is working.
Feb  2 12:11:58 <daemon.notice> Tor[1941]:  Performing bandwidth self-test...done.
Feb  2 14:01:39 <daemon.warning> Tor[1941]:  Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb  2 18:08:11 <daemon.notice> Tor[1941]:  Heartbeat: Tor's uptime is 5:54 hours, with 0 circuits open. I've sent 15.22 MB and received 29.82 MB.
Feb  2 18:08:11 <daemon.notice> Tor[1941]:  Circuit handshake stats since last time: 0/0 TAP, 9/9 NTor.
Feb  2 18:08:11 <daemon.notice> Tor[1941]:  Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 23 v4 connections; and received 11 v1 connections, 25 v2 connections, 0 v3 connections, and 151 v4 connections.
Feb  2 18:44:21 <daemon.warning> Tor[1941]:  Your system clock just jumped 1720 seconds forward; assuming established circuits no longer work.
Feb  2 18:47:08 <daemon.warning> Tor[1941]:  Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb  2 20:29:55 <daemon.warning> Tor[1941]:  Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb  2 21:49:42 <daemon.warning> Tor[1941]:  Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb  2 22:56:29 <daemon.warning> Tor[1941]:  Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb  3 00:08:11 <daemon.notice> Tor[1941]:  Heartbeat: Tor's uptime is 11:18 hours, with 1 circuits open. I've sent 17.56 MB and received 32.43 MB.
Feb  3 00:08:11 <daemon.notice> Tor[1941]:  Circuit handshake stats since last time: 0/0 TAP, 2/2 NTor.
Feb  3 00:08:11 <daemon.notice> Tor[1941]:  Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 25 v4 connections; and received 12 v1 connections, 32 v2 connections, 0 v3 connections, and 174 v4 connections.
Feb  3 02:05:15 <daemon.warning> Tor[1941]:  Your system clock just jumped 106 seconds forward; assuming established circuits no longer work.
Feb  3 05:19:02 <daemon.warning> Tor[1941]:  Your system clock just jumped 105 seconds forward; assuming established circuits no longer work.
Feb  3 06:08:11 <daemon.notice> Tor[1941]:  Heartbeat: Tor's uptime is 17:15 hours, with 1 circuits open. I've sent 18.47 MB and received 34.66 MB.
Feb  3 06:08:11 <daemon.notice> Tor[1941]:  Circuit handshake stats since last time: 0/0 TAP, 1/1 NTor.
Feb  3 06:08:11 <daemon.notice> Tor[1941]:  Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 25 v4 connections; and received 12 v1 connections, 39 v2 connections, 0 v3 connections, and 198 v4 connections.
Feb  3 09:19:20 <daemon.warning> Tor[1941]:  Didn't recognize cell, but circ stops here! Closing circ.
Feb  3 09:19:20 <daemon.warning> Tor[1941]:  circuit_receive_relay_cell (forward) failed. Closing.
Feb  3 10:38:48 <daemon.warning> Tor[1941]:  Your system clock just jumped 105 seconds forward; assuming established circuits no longer work.
Feb  3 12:08:11 <daemon.notice> Tor[1941]:  Heartbeat: Tor's uptime is 23:13 hours, with 2 circuits open. I've sent 19.70 MB and received 36.97 MB.
Feb  3 12:08:11 <daemon.notice> Tor[1941]:  Circuit handshake stats since last time: 1/1 TAP, 1/1 NTor.
Feb  3 12:08:11 <daemon.notice> Tor[1941]:  Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 26 v4 connections; and received 13 v1 connections, 43 v2 connections, 0 v3 connections, and 221 v4 connections.
Feb  3 12:31:37 <daemon.warning> Tor[1941]:  Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb  3 14:43:25 <daemon.warning> Tor[1941]:  Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb  3 16:12:13 <daemon.warning> Tor[1941]:  Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb  3 17:08:00 <daemon.warning> Tor[1941]:  Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb  3 18:09:47 <daemon.warning> Tor[1941]:  Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb  3 18:09:47 <daemon.notice> Tor[1941]:  Heartbeat: Tor's uptime is 1 day 5:06 hours, with 2 circuits open. I've sent 23.34 MB and received 41.04 MB.
Feb  3 18:09:47 <daemon.notice> Tor[1941]:  Circuit handshake stats since last time: 0/0 TAP, 1/1 NTor.
Feb  3 18:09:47 <daemon.notice> Tor[1941]:  Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 35 v4 connections; and received 13 v1 connections, 47 v2 connections, 0 v3 connections, and 264 v4 connections.
Feb  3 19:49:35 <daemon.warning> Tor[1941]:  Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb  3 21:31:23 <daemon.warning> Tor[1941]:  Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.

The "address-hostname" is resolved by a dynamic dns provider in germany (bundesgebaermutter.ddnss.eu) and Atlas/Metrics shows the fqdn of my dial-up connection (xxxx.vodafone-ip.de). And tor is causing only little spikes in the cpu usage graph now. When the consensus diffs were computed it took half an hour or more at 100 percent on the poor bPi SoC.

Granted, it is a low-volume relay. Maybe I should just shut up ;)

Child Tickets

Change History (6)

comment:1 Changed 17 months ago by teor

Milestone: Tor: 0.3.2.x-finalTor: 0.3.4.x-final

These feature and bugfix tickets have no patches. The earliest they will get done is 0.3.4.

comment:2 Changed 16 months ago by nickm

Keywords: 034-triage-20180328 added

comment:3 Changed 16 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:4 Changed 15 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:5 Changed 10 months ago by bundesgebaermutter

It seems that 0.3.4 has fixed this bug unexpectedly. Once I upgraded to 0.3.4.7-rc a few weeks ago the warnings were gone. I was so accustomed to them that I really did not notice their missing at first.

Additionally, if you take a look at the https://docs.armbian.com/Release_Changelog/ of 5.6.0 you can see a "fixed clock drift on Bananapi boards". I guess, in my case, it has nothing to do with it, because I have never seen a clock drift. But maybe it is useful in the future.

comment:6 Changed 9 months ago by teor

Resolution: fixed
Status: newclosed

We resolved this issue in 0.3.4, possibly by changing how events worked.

Note: See TracTickets for help on using tickets.