Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #16608

Closed (moved)
Open
Opened Jul 17, 2015 by toralf@toralf

"time published in the consensus network status" seems to be wrong

I setup a watch dog script which informs me immediately about such log messages. I checked immediately the time. The time at my server was the same at my desktop and both seems to be accurate (set by ntpd).

That's why I do assume that this log

Jul 17 10:58:58.000 [warn] Our clock is 1 minutes, 2 seconds behind the time published in the consensus network status document (2015-07-17 09:00:00 UTC).  Tor needs an accurate clock to work correctly. Please check your time and date settings!

points to an issue which has nothing to do with a wrong local clock of my server (F1BE15429B3CE696D6807F4D4A58B1BFEC45C822)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#16608