Opened 3 years ago

Closed 3 years ago

#17654 closed defect (fixed)

0.2.8.0-dev crashes soon after boot on Linux

Reported by: ciborgue Owned by: nickm
Priority: High Milestone: Tor: 0.2.8.x-final
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Blocker Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Nov 22 13:34:12.000 [notice] This version of Tor (0.2.8.0-alpha-dev) is newer than any recommended version, according to the directory authorities. Recommended versions are: 0.2.4.23,0.2.4.24,0.2.4.25,0.2.4.26,0.2.4.27,0.2.5.8-rc,0.2.5.9-rc,0.2.5.10,0.2.5.11,0.2.5.12,0.2.6.5-rc,0.2.6.6,0.2.6.7,0.2.6.8,0.2.6.9,0.2.6.10,0.2.7.1-alpha,0.2.7.2-alpha,0.2.7.3-rc,0.2.7.4-rc,0.2.7.5
Nov 22 13:34:15.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Nov 22 13:34:15.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Nov 22 13:34:15.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Nov 22 13:34:16.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Nov 22 13:34:18.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Nov 22 13:34:18.000 [notice] Bootstrapped 100%: Done
Nov 22 13:35:16.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Nov 22 13:35:21.000 [notice] Performing bandwidth self-test...done.
Nov 22 13:36:53.000 [notice] Your DNS provider gave an answer for "5ulaoeeh.invalid", which is not supposed to exist. Apparently they are hijacking DNS failures. Trying to correct for this. We've noticed 2 possibly bad addresses so far.
Nov 22 13:36:53.000 [notice] Your DNS provider has given "198.105.244.24" as an answer for 9 different invalid addresses. Apparently they are hijacking DNS failures. I'll try to correct for this by treating future occurrences of "198.105.244.24" as 'not found'.
Nov 22 14:00:20.000 [err] tor_assertion_failed_(): Bug: src/or/connection_or.c:1483: connection_tls_continue_handshake: Assertion !tor_tls_is_server(conn->tls) failed; aborting. (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: Assertion !tor_tls_is_server(conn->tls) failed in connection_tls_continue_handshake at src/or/connection_or.c:1483. Stack trace: (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/bin/tor(log_backtrace+0x46) [0x7f9f20ac5186] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0xe4) [0x7f9f20ae3594] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/bin/tor(connection_tls_continue_handshake+0x38e) [0x7f9f20a412de] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/bin/tor(+0x21f209) [0x7f9f20a29209] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/bin/tor(+0xc9c55) [0x7f9f208d3c55] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x754) [0x7f9f1cf00f24] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/bin/tor(do_main_loop+0x32d) [0x7f9f208d520d] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/bin/tor(tor_main+0x1cb5) [0x7f9f208d9395] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /usr/bin/tor(main+0x1c) [0x7f9f208cbe4c] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)
Nov 22 14:00:20.000 [err] Bug: /lib/x86_64-linux-gnu/libc.so.6(libc_start_main+0xf5) [0x7f9f1c2f7ec5] (on Tor 0.2.8.0-alpha-dev cbc1b8a4f75d449a)

Child Tickets

Change History (7)

comment:1 Changed 3 years ago by teor

This assertion was introduced on 8 Oct 2015 by nickm in 9d019a7db725dca3dfdbf8d4dbc3b51835e0b49e.

comment:2 Changed 3 years ago by nickm

Priority: MediumHigh
Severity: MajorBlocker

comment:3 Changed 3 years ago by teor

apx on #tor-dev reports that two of their servers crash every 20 minutes with:

Nov 25 00:29:55.000 [err] tor_assertion_failed_(): Bug: src/or/connection_or.c:1483: connection_tls_continue_handshake: Assertion !tor_tls_is_server(conn->tls) failed; aborting. (on Tor 0.2.8.0-alpha-dev 6cdd024c94ce9d2b)
Nov 25 00:29:55.000 [err] Bug: Assertion !tor_tls_is_server(conn->tls) failed in connection_tls_continue_handshake at src/or/connection_or.c:1483. Stack trace: (on Tor 0.2.8.0-alpha-dev 6cdd024c94ce9d2b)

They have a full debug log and will hopefully attach it to this ticket.

comment:4 Changed 3 years ago by nickm

Owner: set to nickm
Status: newaccepted

comment:5 Changed 3 years ago by nickm

Status: acceptedneeds_review

Please test bug17654_try1 in my public repository?

comment:6 in reply to:  5 Changed 3 years ago by dgoulet

Replying to nickm:

Please test bug17654_try1 in my public repository?

Been going strong for an hour and a half on both a fast relay and client (which wasn't possible before). I say merge :).

comment:7 Changed 3 years ago by nickm

Resolution: fixed
Status: needs_reviewclosed

Thanks for testing; just merged it!

Note: See TracTickets for help on using tickets.