Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2572

Closed (moved)
(moved)
Open
Created Feb 16, 2011 by Robert Ransom@rransom

Bridge authority crashes on SIGHUP

Tonga has crashed twice, once on January 31, again when it was restarted on February 16:

Feb 16 06:25:01.238 [notice] Tor 0.2.2.22-alpha (git-21b3de6cf37d4e60) opening new log file. Feb 16 06:25:01.327 [err] Unable to add own descriptor to directory: Skipping router descriptor: not in consensus. Feb 16 06:25:01.327 [warn] options_act(): Bug: Error initializing keys; exiting Feb 16 06:25:01.327 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying.

Both crashes were at the same time of day, and with identical log messages. Tonga is now running 0.2.1.29 again as a stopgap measure, but we need to find and fix this problem.

The "Skipping router descriptor: not in consensus." message came from src/or/routerlist.c line 3313, in router_add_to_routerlist. The only changes 'git blame' turned up earlier in that function that are present in 0.2.2.22-alpha and not in 0.2.1.29 were made in 9ca311f6 (Allow using regular relays as bridges).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking