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

Closed (moved)
Open
Opened Aug 19, 2011 by Nick Mathewson@nickm🥄

Bufferevent-based server sometimes succeeds, sometimes fails.

Sebastian reports that his server (debian, tor master, libevent patches-2.0) gets lots of "TLS error while handshaking (with bufferevent) with [scrubbed]: ssl handshake failure (in SSL routines:SSL3_READ_BYTES:SSL3_ST_SR_CERT_A)" warnings. Those imply that (some? all?) connections aren't making it in.

Additionally, his circuit timeouts seem to increase and increase. Perhaps some outgoing connections aren't working.

So tentatively, I'm going to guess that the situation is: sometimes outgoing connections succeed, and sometimes they fail. Sometimes incoming connections succeed, and sometimes they fail.

The first thing to ask is, is that right? Or was I mistaken when I thought that incoming connections work sometimes?

Second thing to ask is, is there any pattern to which hosts work and which don't? Are hosts in "mostly working" and "mostly not working" classes, or does each conn fail more or less at random? Are the ones that work with incoming conns the same as the ones that work with outgoing conns?

To upload designs, you'll need to enable LFS and have an 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#3769