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

Closed (moved)
Open
Opened Mar 24, 2017 by teor@teor

Port rebind should not be performed after soft accounting limit reached

A relay operator reports:

  • their relay had accounting set
  • it reached the soft limit and marked all connections for close
  • when the period ended, it estimated that it would be active for the entire period
  • then it attempted to rebind to ports, even though it had never closed the listeners

This appears to be a simple state management issue: https://lists.torproject.org/pipermail/tor-relays/2017-March/012151.html

I don't think the issue is restricted to OpenBSD.

I don't know if it's a regression, and I don't know if it should be fixed in 0.3.0. Given how annoying and confusing it is, we should probably backport it.

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#21810