Opened 8 years ago

Closed 6 years ago

#4753 closed defect (fixed)

Tor Client Bug: "connection_stop_reading: Assertion conn->read_event failed; aborting."

Reported by: zhenling Owned by:
Priority: Medium Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version: Tor: 0.2.2.39
Severity: Keywords: Transparent Proxy tor-client
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The Tor client was configured as a transparent proxy at the gateway, however, it crashed a couple of days ago.
Here is the log from Tor:

"Nov 25 23:35:15.850 [err] connection_stop_reading(): Bug: main.c:338: connection_stop_reading: Assertion conn->read_event failed; aborting.
main.c:338 connection_stop_reading: Assertion conn->read_event failed; aborting."

Child Tickets

Change History (9)

comment:1 Changed 8 years ago by nickm

Milestone: Tor: 0.2.2.x-final
Summary: Tor Client BugTor Client Bug: "connection_stop_reading: Assertion conn->read_event failed; aborting."

This is with version 0.2.2.34 ? If so, please make sure you upgrade to 0.2.2.35.

Did you get a core dump at all with this? If so, knowing the value of *conn at the time of failure would help a lot.

comment:2 Changed 7 years ago by nickm

Status: newneeds_information

comment:3 Changed 7 years ago by nickm

Resolution: user disappeared
Status: needs_informationclosed

comment:4 Changed 7 years ago by nickm

Keywords: tor-client added

comment:5 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:6 Changed 6 years ago by i

Resolution: user disappeared
Status: closedreopened
Version: Tor: 0.2.2.34Tor: 0.2.2.39

This assertion was triggered at least twice over the last week for me. Below you find the last log messages just before the assertion fails. I could probably get a coredump, but it's an embedded device and would require a significant amount of work (and who knows if it'll happen again). Do you think you can work with the log messares alone?

# tor --version
Aug 11 00:14:39.644 [notice] Tor v0.2.2.39 (git-bec76476efb71549). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i586)
Tor version 0.2.2.39 (git-bec76476efb71549).

Log messages:

Aug 10 22:23:15.146 [info] connection_edge_package_raw_inbuf(): called with package_window 0. Skipping.
Aug 10 22:23:15.226 [info] evdns_server_callback(): Got a new DNS request!
Aug 10 22:23:15.229 [info] evdns_server_callback(): Passing request for [scrubbed] to rewrite_and_attach.
Aug 10 22:23:15.235 [info] exit (high-uptime) circ (length 3): WilliamCZ6(open) Karlstad(open) bolobolo1(open)
Aug 10 22:23:15.239 [info] connection_ap_handshake_send_resolve(): Address sent for resolve, ap socket -1, n_circ_id 32008
Aug 10 22:23:15.242 [info] evdns_server_callback(): Passed request for [scrubbed] to rewrite_and_attach_if_allowed.
Aug 10 22:23:15.426 [info] connection_edge_package_raw_inbuf(): called with package_window 0. Skipping.
Aug 10 22:23:15.494 [err] connection_stop_reading(): Bug: main.c:338: connection_stop_reading: Assertion conn->read_event failed; aborting.
main.c:338 connection_stop_reading: Assertion conn->read_event failed; aborting.
Aborted

comment:7 Changed 6 years ago by nickm

Hm. It's not immediately obvious from the log message. But the 0.2.2.x series isn't seriously supported any more; are you able to try the latest 0.2.3.x or 0.2.4.x release?

comment:8 Changed 6 years ago by i

Status: reopenedneeds_information

I have now installed Tor v0.2.3.25 (git-17c24b3118224d65), built with the same compiler, and will see how this behaves. The reason I chose this rather than the 0.2.4 series is that I prefer code declared “stable”. I'm setting this bug to “needs information” and will update again if I hit the assertion or I get the impression it's not going to happen again.

comment:9 Changed 6 years ago by i

Resolution: fixed
Status: needs_informationclosed

I haven't hit this issue with 0.2.3.25 in 11 days. Instead I have hit #6673. Closing this bug once again.

Note: See TracTickets for help on using tickets.