[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: clock jump in 0.2.0.23-rc, too



     Here is some of yesterday's notice-level log from my tor (0.2.0.23-rc)
server:

Apr 04 05:34:37.285 [warn] Your system clock just jumped 133 seconds forward; assuming established circuits no longer work.
Apr 04 05:43:23.629 [warn] Your system clock just jumped 140 seconds forward; assuming established circuits no longer work.
Apr 04 09:30:27.029 [warn] Your system clock just jumped 121 seconds forward; assuming established circuits no longer work.
Apr 04 09:35:30.627 [warn] Your system clock just jumped 104 seconds forward; assuming established circuits no longer work.
Apr 04 09:49:34.378 [warn] Your system clock just jumped 106 seconds forward; assuming established circuits no longer work.
Apr 04 10:00:42.032 [warn] Your system clock just jumped 111 seconds forward; assuming established circuits no longer work.
Apr 04 10:24:09.684 [warn] Your system clock just jumped 110 seconds forward; assuming established circuits no longer work.
Apr 04 11:17:36.702 [warn] Your system clock just jumped 126 seconds forward; assuming established circuits no longer work.
Apr 04 11:21:22.129 [warn] Your system clock just jumped 133 seconds forward; assuming established circuits no longer work.
Apr 04 11:25:26.342 [warn] Your system clock just jumped 163 seconds forward; assuming established circuits no longer work.
Apr 04 11:30:26.061 [warn] Your system clock just jumped 117 seconds forward; assuming established circuits no longer work.
Apr 04 11:33:36.188 [warn] Your system clock just jumped 126 seconds forward; assuming established circuits no longer work.
Apr 04 11:43:34.353 [warn] Your system clock just jumped 110 seconds forward; assuming established circuits no longer work.
Apr 04 11:49:46.641 [warn] Your system clock just jumped 112 seconds forward; assuming established circuits no longer work.
Apr 04 11:57:48.956 [warn] Your system clock just jumped 116 seconds forward; assuming established circuits no longer work.
Apr 04 12:08:02.819 [warn] Your system clock just jumped 122 seconds forward; assuming established circuits no longer work.
Apr 04 12:23:38.767 [warn] Your system clock just jumped 118 seconds forward; assuming established circuits no longer work.
Apr 04 12:27:52.359 [warn] Your system clock just jumped 193 seconds forward; assuming established circuits no longer work.
Apr 04 12:34:25.515 [warn] Your system clock just jumped 149 seconds forward; assuming established circuits no longer work.

     Each time one of those messages occurs, tor kills all its open circuits,
so you can see that it was being basically pretty useless as a server.  I gave
it a SIGINT to shut it down, and once again it took approximately *55 seconds*
to acknowledge receipt of SIGINT in the log.

Apr 04 13:16:18.867 [notice] Interrupt: will shut down in 1500 seconds. Interrupt again to exit now.
Apr 04 13:41:18.700 [notice] Clean shutdown finished. Exiting.

     Once the shutdown had completed, I swapped 0.2.0.23-rc for 0.2.0.19-alpha,
the last release that did *not* have the clock jump bug, to the best of my
recollection.  I have since given it a SIGHUP once to get it to change circuits
for me for a long download.

Apr 04 14:01:33.196 [notice] Tor 0.2.0.19-alpha (r13450) opening log file.
Apr 04 14:01:33.196 [warn] Can't log to stdout with RunAsDaemon set; skipping stdout
Apr 04 14:01:33.767 [notice] Your Tor server's identity key fingerprint is 'MYCROFTsOtherChild 0232 2050 5A55 0D6F DF0C 20FF 7C48 E66B A06A 49A6'
Apr 04 14:01:34.177 [warn] Please upgrade! This version of Tor (0.2.0.19-alpha) is not recommended, according to the directory authorities. Recommended versions are: 0.1.2.19,0.2.0.22-rc,0.2.0.23-rc
Apr 04 14:01:42.424 [notice] We now have enough directory information to build circuits.
Apr 04 14:01:42.558 [warn] Nickname list includes 'yourd0f670b45a' which isn't a known router.
Apr 04 14:01:44.518 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Apr 04 14:01:45.345 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 04 14:02:45.827 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Apr 04 14:03:34.106 [notice] Performing bandwidth self-test...done.
Apr 04 20:15:05.533 [notice] Client asked for the mirrored directory, but we don't have a good one yet. Sending 503 Dir not available.
Apr 04 20:48:48.228 [notice] Received reload signal (hup). Reloading config.
Apr 04 20:48:48.233 [notice] Tor 0.2.0.19-alpha (r13450) opening log file.
Apr 04 20:48:48.234 [warn] Can't log to stdout with RunAsDaemon set; skipping stdout
Apr 04 20:48:48.234 [warn] Can't log to stdout with RunAsDaemon set; skipping stdout
Apr 04 20:48:48.666 [warn] Nickname list includes 'yourd0f670b45a' which isn't a known router.
Apr 04 21:21:11.997 [warn] Please upgrade! This version of Tor (0.2.0.19-alpha) is not recommended, according to the directory authorities. Recommended versions are: 0.1.2.19,0.2.0.22-rc,0.2.0.23-rc

     Those are all of the messages issued thus far, so 0.2.0.19-alpha has been
running with no problems for over 25 hours.  I will continue to watch the list
for news of a new release to try, but for now, the *-rc versions are quite
unusable as servers.


                                  Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet:       bennett at cs.niu.edu                              *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."                                               *
*    -- Gov. John Hancock, New York Journal, 28 January 1790         *
**********************************************************************