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
  • #27040

Closed (moved)
Open
Opened Aug 05, 2018 by Roger Dingledine@arma

[warn] We don't have a consensus, so we can't perform v2 rendezvous operations.

Start your Tor, and while it's bootstrapping, make an onion service request. (In my case I started 'apt-get update' which uses the apt-transport trick to make it use my Tor.)

Now I have in my logs:

Jul 30 20:27:11.890 [notice] Bootstrapped 25%: Loading networkstatus consensus
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.286 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.286 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.379 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.379 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.384 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.384 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.385 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.385 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:58.498 [notice] Bootstrapped 45%: Asking for relay descriptors

I think maybe it shouldn't warn like that if it hasn't bootstrapped yet? Or, is there some specific value to warning there?

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