Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#2523 closed defect (fixed)

Computer clock is potentially incorrect

Reported by: snuggleywuggle Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: tor clock incorrect dirserv tor-client
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

'Hi,

After approximately 3 hours of running Tor/Vidalia, I find that all my network connections drop off, and the following error message appears in the log.

[20:14:37] Your Computer's Clock is Potentially Incorrect - Tor has determined that your computer's clock may be set to 28730 seconds in the past compared to the source "DIRSERV:109.123.119.163:9030". If your clock is not correct, Tor will not be able to function. Please verify your computer displays the correct time.

I don't know if this stops things working or not, but though I'd check.

The advanced log doesn't mention the time (see below)

Feb 09 17:43:59.230 [Notice] Tor v0.2.1.29 (r8e9b25e6c7a2e70c). This is experimental software. Do not rely on it for strong anonymity. (Running on Very recent version of Windows [major=6,minor=1] [workstation] {terminal services, single user})
Feb 09 17:43:59.230 [Notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.
Feb 09 17:43:59.557 [Notice] Initialized libevent version 1.4.14-stable using method win32. Good.
Feb 09 17:43:59.557 [Notice] Opening OR listener on 0.0.0.0:8080
Feb 09 17:43:59.557 [Notice] Opening Directory listener on 0.0.0.0:9030
Feb 09 17:43:59.557 [Notice] Opening Control listener on 127.0.0.1:9051
Feb 09 17:43:59.667 [Notice] Parsing GEOIP file.
Feb 09 17:44:08.122 [Notice] OpenSSL OpenSSL 0.9.8p 16 Nov 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Feb 09 17:44:08.122 [Notice] Your Tor server's identity key fingerprint is 'FreeSpeechFTW 840036971430F1208C0B723E8173372B40F555D8'
Feb 09 17:44:08.122 [Notice] We now have enough directory information to build circuits.
Feb 09 17:44:08.122 [Notice] Bootstrapped 80%: Connecting to the Tor network.
Feb 09 17:44:08.122 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
Feb 09 17:44:08.137 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
Feb 09 17:44:09.011 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Feb 09 17:44:09.011 [Notice] Bootstrapped 100%: Done.
Feb 09 17:44:09.011 [Notice] Now checking whether ORPort MY IP ADDRESS HERE:8080 and DirPort MY IP ADDRESS HERE:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Feb 09 17:44:10.883 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Feb 09 17:44:22.946 [Notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Feb 09 17:45:13.581 [Notice] Performing bandwidth self-test...done.

Child Tickets

Change History (5)

comment:1 Changed 9 years ago by phobos

The simple question is if you sync to a timeserver of some sort, if not, you should. It's also possible the dirserver referenced is out of sync.

comment:2 Changed 9 years ago by arma

See also #1074 and #2528 for related bugs.

comment:3 Changed 9 years ago by arma

Resolution: fixed
Status: newclosed

Ok. When 0.2.1.30 comes out (sometime this month hopefully), this problem should be gone. Thanks!

comment:4 Changed 7 years ago by nickm

Keywords: tor-client added

comment:5 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.