Re: Your system clock just jumped 130 seconds forward; assuming established circuits no longer work.

[Scott Bennett <bennett@xxxxxxxxxx>]

     On Tue, 6 Oct 2009 04:02:15 +0200 Lucky Green <shamrock@xxxxxxxxxxxxxx>
wrote:
>On Mon, Oct 05, 2009 at 10:53:52PM +0200, Eugen Leitl wrote:
>> 
>> I've decided to move my middleman to a Linux box, and now I
>> see logs full of
>> 
>> Oct 05 22:42:19.097 [warn] eventdns: All nameservers have failed
>> Oct 05 22:42:40.280 [notice] Bootstrapped 90%: Establishing a Tor circuit.
>> Oct 05 22:42:48.065 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
>> Oct 05 22:42:48.065 [notice] Bootstrapped 100%: Done.
>> Oct 05 22:42:48.065 [notice] Now checking whether ORPort 95.91.107.132:9001 and DirPort 95.91.107.132:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
>> Oct 05 22:42:50.635 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
>> Oct 05 22:43:31.516 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
>> Oct 05 22:43:45.918 [notice] Performing bandwidth self-test...done.
>> Oct 05 22:45:32.791 [warn] Your system clock just jumped 101 seconds forward; assuming established circuits no longer work.
>
>Eugen,
>See my post for a possible fix:
>http://archives.seul.org/or/talk/Mar-2008/msg00226.html
>
>Note that the TCS timer issues in the above post can happen on any 
>multicore system, not just under VMware.
>
     Fascinating.  Why does the LINUX kernel allow the TSC values to differ
by so much?
     In any case, by all means, Eugen should try that first.  If that resolves
the matter for him, that's great.  If it doesn't, then I'd suggest that he see
whether his ISP can diagnose and fix a problem with his Internet connection.
My experiences with the clock jumps in tor were on a FreeBSD system and appear
to be related to stoppages in my Internet connection.

					Scott
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/