On Aug 8, 2011, at 3:59 PM, Softail wrote:

Every few days I find a log message like this

Aug 08 07:20:09.241 [warn] Your system clock just jumped 122 seconds forward; assuming established circuits no longer work.

Seems to always be 122 seconds as far as I can tell and happens at random times. Doesn't seem to be correlated with the log rotations or anything else. I'm running ntpd and that seems to be working fine. I started to let it use the kludge local clock in case the network was unavailable. I didn't think that was likely and it doesn't seem to have made any difference. Google turns up some complaints about this on much older versions 2.0.23. I'm currently running 2.1.30 from the Tor repository. It's i386 running on x86_64.

I have this exact same problem about every 12 hours, always 122 seconds. As far as I can tell my system clock is never more than 1-2 seconds off. I'm running 2.3.2-alpha on a PPC OSX 10.4 machine.

I suppose I could try rebuilding a 64 bit version but so far haven't built my own yet. Would eventually like to dig into the sources but don't have time right now.

I built my own from scratch, with and without static libraries. Hasn't helped.

Anybody else see this or have suggestions about what to do about it?

I'm not particularly annoyed by the log entries, but I would like to know what effect it's having on my node. Are there any consequences besides a few circuits dropping every 12 hours?

~Justin Aplin

On Monday 08 August 2011 15:59:02 Softail wrote:

Every few days I find a log message like this

Aug 08 07:20:09.241 [warn] Your system clock just jumped 122 seconds forward; assuming established circuits no longer work.

Anybody else see this or have suggestions about what to do about it?

Jun 23 03:13:55 darner Tor[1061]: Your system clock just jumped 117 seconds forward; assuming established circuits no longer work. Jun 23 04:00:36 darner Tor[1061]: Your system clock just jumped 110 seconds forward; assuming established circuits no longer work. Jun 23 04:02:57 darner Tor[1061]: Your system clock just jumped 142 seconds forward; assuming established circuits no longer work. Jun 24 03:15:22 darner Tor[1061]: Your system clock just jumped 103 seconds forward; assuming established circuits no longer work. Jun 24 04:17:02 darner Tor[1061]: Your system clock just jumped 160 seconds forward; assuming established circuits no longer work. Jun 24 04:19:11 darner Tor[1061]: Your system clock just jumped 130 seconds forward; assuming established circuits no longer work. Jun 25 05:55:48 darner Tor[1061]: Your system clock just jumped 161 seconds forward; assuming established circuits no longer work. Jun 25 06:18:32 darner Tor[1061]: Your system clock just jumped 103 seconds forward; assuming established circuits no longer work. Jun 25 06:21:08 darner Tor[1061]: Your system clock just jumped 157 seconds forward; assuming established circuits no longer work.

I thought it was caused by the Hammer maintenance, which runs every night; but that starts at 5:00 UTC, so that wouldn't explain a jump at 4:00.