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

Closed (moved)
(moved)
Open
Created Jun 04, 2013 by Trac@tracbot

Crash in assert_connection_ok

After somewhere between a few and 24 hours, Tor on my exit node crashes with the same log message. This has happened every day for the past 3.

Jun 4 08:14:47 tor Tor[24513]: connection_exit_connect(): Bug: newly connected conn had data waiting! Jun 4 08:14:57 tor Tor[24513]: assert_connection_ok(): Bug: connection.c:4066: assert_connection_ok: Assertion (conn->type == CONN_TYPE_EXIT && conn->state == EXIT_CONN_STATE_RESOLVING) || connection_is_writing(conn) || conn->write_blocked_on_bw || (CONN_IS_EDGE(conn) && TO_EDGE_CONN(conn)->edge_blocked_on_circ) failed; aborting.

Jun 04 15:48:12.279 [notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on OpenBSD. (5.3, amd64) Jun 04 15:48:12.289 [notice] Initialized libevent version 1.4.14b-stable using method kqueue. Good.

Trac:
Username: usuality

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