more clock jump messages from 0.2.0.22-rc

Tue Apr 1 01:19:31 UTC 2008

     0.2.0.22-rc continues to complain of clock jumps, even though I can find
no evidence that such have occurred.  Relevant background information includes:

	--the operating system is FreeBSD 6.3-STABLE, a tried-and-true system
	  used on major servers worldwide
	--cron runs ntpdate hourly at 17 minutes past the hour to synchronize
	  the system clock with the NIST time servers
	--my Internet connection was down this morning from 05:01:25 till
	  07:22:10, which includes the times of the first few messages below,
	  so ntpdate would not have altered the system clock during that time

Here are today's relevant messages from 0.2.0.22-rc:

Mar 31 06:36:26.955 [warn] Your system clock just jumped 115 seconds forward; assuming established circuits no longer work.
Mar 31 06:38:22.028 [warn] Your system clock just jumped 116 seconds forward; assuming established circuits no longer work.
Mar 31 06:40:17.083 [warn] Your system clock just jumped 115 seconds forward; assuming established circuits no longer work.
Mar 31 06:42:12.149 [warn] Your system clock just jumped 115 seconds forward; assuming established circuits no longer work.
Mar 31 06:44:07.205 [warn] Your system clock just jumped 115 seconds forward; assuming established circuits no longer work.
Mar 31 06:46:11.267 [warn] Your system clock just jumped 124 seconds forward; assuming established circuits no longer work.

     As you can see, the messages above began coming so fast that less than a
second elapsed between them.  (Add the number of seconds allegedly jumped to
the timestamp, and you'll see what I mean.)
     When the Internet connection was restored, the following appeared, due to
a new IP address having been assigned by the ISP's PPPoE server:

Mar 31 07:26:02.908 [notice] Your IP address seems to have changed to 66.225.36.50. Updating.
Mar 31 07:26:16.244 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Mar 31 07:26:18.639 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 31 07:26:42.368 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Mar 31 07:28:30.592 [notice] Performing bandwidth self-test...done.
Mar 31 08:15:03.840 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Mar 31 08:15:03.841 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Mar 31 09:48:15.771 [warn] Your system clock just jumped 115 seconds forward; assuming established circuits no longer work.
Mar 31 10:22:03.184 [warn] Your system clock just jumped 102 seconds forward; assuming established circuits no longer work.
Mar 31 10:30:44.870 [warn] Your system clock just jumped 123 seconds forward; assuming established circuits no longer work.
Mar 31 10:48:18.673 [warn] Your system clock just jumped 139 seconds forward; assuming established circuits no longer work.
Mar 31 12:20:13.316 [warn] Your system clock just jumped 116 seconds forward; assuming established circuits no longer work.
Mar 31 13:12:22.667 [warn] Your system clock just jumped 110 seconds forward; assuming established circuits no longer work.
Mar 31 13:34:31.505 [warn] Your system clock just jumped 144 seconds forward; assuming established circuits no longer work.
Mar 31 13:37:00.677 [warn] Your system clock just jumped 149 seconds forward; assuming established circuits no longer work.
Mar 31 13:57:56.749 [warn] Your system clock just jumped 161 seconds forward; assuming established circuits no longer work.
Mar 31 14:17:32.753 [warn] Your system clock just jumped 139 seconds forward; assuming established circuits no longer work.
Mar 31 14:48:46.974 [warn] Your system clock just jumped 122 seconds forward; assuming established circuits no longer work.
Mar 31 14:50:51.721 [warn] Your system clock just jumped 125 seconds forward; assuming established circuits no longer work.

     Server traffic, of course, had dropped to nearly zero at this point.
Figuring that restarting tor might, as I had previously observed, stop the
problem, I did so.  Restarting also allowed me to upgrade to 0.2.0.23-rc, and
thus far, the problem has not recurred.  However, unless the problem was
addressed in the changes made between 0.2.0.22-rc and 0.2.0.23-rc, the problem
is likely to return.

Mar 31 15:13:21.073 [notice] Interrupt: will shut down in 1500 seconds. Interrupt again to exit now.
Mar 31 15:16:39.914 [warn] Your system clock just jumped 145 seconds forward; assuming established circuits no longer work.

     I should add that there was an uncommonly long delay, at least 10 seconds
and probably more like 15, between my hitting the enter key with the second
"kill -INT `cat /var/run/tor/tor.pid`" command and the following message.  The
system was ~99% idle at the time.

Mar 31 15:18:05.510 [notice] Sigint received a second time; exiting now.

     If anyone else is seeing this weird clock jump message when no clock jumps
appear to be happening, please post any information you have about it to the
list.
     Thanks much.

                                  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         *
**********************************************************************