Re: [tor-bugs] #16013 [Tor]: Assertion ENTRY_TO_CONN(conn)->state == AP_CONN_STATE_CIRCUIT_WAIT failed in circuit_get_open_circ_or_launch at circuituse.c:1835

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#16013: Assertion ENTRY_TO_CONN(conn)->state == AP_CONN_STATE_CIRCUIT_WAIT failed
in circuit_get_open_circ_or_launch at circuituse.c:1835
------------------------+-------------------------------
     Reporter:  slrsab  |      Owner:
         Type:  defect  |     Status:  needs_information
     Priority:  normal  |  Milestone:
    Component:  Tor     |    Version:  Tor: unspecified
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-------------------------------

Comment (by cypherpunks):

 {{{
 I hit this same assert fail, output here:

 Jun 04 XX:39:28 host Tor[310]: Received reload signal (hup). Reloading
 config and resetting internal state.
 Jun 04 XX:39:28 host Tor[310]: Read configuration file "/etc/tor/torrc".
 Jun 04 XX:45:03 host Tor[310]: New control connection opened from
 127.0.0.1.
 Jun 04 XX:50:41 host Tor[310]: New control connection opened from
 127.0.0.1.
 Jun 04 XX:50:42 host Tor[310]: Query '[scrubbed]' didn't have valid rend
 desc in cache. Failing.
 Jun 04 XX:50:42 host Tor[310]: tor_assertion_failed_(): Bug:
 src/or/circuituse.c:1835: circuit_get_open_circ_or_launch: Assertion
 ENTRY_TO_CONN(conn)->state == AP_CONN_STATE_CIRCUIT_WAIT failed; aborting.
 Jun 04 XX:50:42 host Tor[310]: Bug: Assertion ENTRY_TO_CONN(conn)->state
 == AP_CONN_STATE_CIRCUIT_WAIT failed in circuit_get_open_circ_or_launch at
 src/or/circuituse.c:1835. Stack trace:
 Jun 04 XX:50:42 host Tor[310]: Bug:     /usr/bin/tor(log_backtrace+0x41)
 [0x2661fa8631]
 Jun 04 XX:50:42 host Tor[310]: Bug:
 /usr/bin/tor(tor_assertion_failed_+0x8c) [0x2661fb62fc]
 Jun 04 XX:50:42 host Tor[310]: Bug:     /usr/bin/tor(+0xb7a8f)
 [0x2661f45a8f]
 Jun 04 XX:50:42 host Tor[310]: Bug:
 /usr/bin/tor(connection_ap_handshake_attach_circuit+0x2d9) [0x2661f46529]
 Jun 04 XX:50:42 host Tor[310]: Bug:
 /usr/bin/tor(connection_ap_attach_pending+0x79) [0x2661f64159]
 Jun 04 XX:50:42 host Tor[310]: Bug:
 /usr/bin/tor(circuit_build_needed_circs+0x38) [0x2661f45448]
 Jun 04 XX:50:42 host Tor[310]: Bug:     /usr/bin/tor(+0x360d8)
 [0x2661ec40d8]
 Jun 04 XX:50:42 host Tor[310]: Bug:
 /usr/lib/libevent-2.0.so.5(event_base_loop+0x806) [0x2badaa5dca6]
 Jun 04 XX:50:42 host Tor[310]: Bug:     /usr/bin/tor(do_main_loop+0x17d)
 [0x2661ec4bed]
 Jun 04 XX:50:42 host Tor[310]: Bug:     /usr/bin/tor(tor_main+0x16a5)
 [0x2661ec79f5]
 Jun 04 XX:50:42 host Tor[310]: Bug:
 /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x2bad9b8b790]
 Jun 04 XX:50:42 host Tor[310]: Bug:     /usr/bin/tor(_start+0x29)
 [0x2661ec1139]
 Jun 04 XX:50:42 host systemd[1]: tor.service: main process exited,
 code=killed, status=6/ABRT
 Jun 04 XX:50:42 host systemd[1]: Unit tor.service entered failed state.
 Jun 04 XX:50:42 host systemd[1]: tor.service failed.

 When it occurred:

 added a new HidServAuth torrc config line for a stealth hs (foo.onion)
 ran `kill -SIGHUP $TOR_PID` to force a config reload
 ran `torsocks ssh foo.onion`

 Arch Linux, x86_64
 Tor v0.2.6.8 (git-5c8440b13bde6c88) running on Linux with Libevent
 2.0.22-stable, OpenSSL 1.0.2a and Zlib 1.2.8.
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16013#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs