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

Closed (moved)
Open
Opened Jan 06, 2018 by Trac@tracbot

Our directory information is no longer up-to-date

Jan 06 16:22:12.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Jan 06 16:22:12.000 [notice] Read configuration file "/etc/tor/tor2.cfg". Jan 06 16:22:12.000 [notice] Tor 0.3.1.9 (git-df96a13e9155c7bf) opening log file. Jan 06 16:26:09.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Jan 06 16:26:09.000 [notice] Read configuration file "/etc/tor/tor2.cfg". Jan 06 16:26:09.000 [notice] Tor 0.3.1.9 (git-df96a13e9155c7bf) opening log file. Jan 06 16:28:01.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We're missing descriptors for some of our primary entry guards Jan 06 16:28:01.000 [notice] I learned some more directory information, but not enough to build a circuit: We're missing descriptors for some of our primary entry guards Jan 06 16:28:01.000 [warn] Requested exit point '$D885444EED4522249A1BD29A250E612889C451F8' is not known. Closing. Jan 06 16:28:11.000 [warn] Giving up launching first hop of circuit to rendezvous point .......... Jan 06 16:28:11.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Jan 06 16:28:11.000 [notice] Read configuration file "/etc/tor/tor.cfg". Jan 06 16:28:12.000 [notice] Tor 0.3.1.9 (git-df96a13e9155c7bf) opening log file. Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to rendezvous point ............ Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to rendezvous point ............ Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to rendezvous point ............ Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to rendezvous point ............ Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to rendezvous point ............ Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to rendezvous point ............ ........

Waited for an hour for Tor to repair itself but it was just throwing 'giving up' warning.

Server was running 250 domains, not DDoSed, up to 200 users connected.

The first time this problem occur couple of days on Tor instance running only 1 domain but it was online for days.

Trac:
Username: cstest

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