Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#22879 closed defect (duplicate)

Tor fails to start (assert)

Reported by: ram Owned by:
Priority: High Milestone: Tor: 0.3.1.x-final
Component: Core Tor/Tor Version: Tor: 0.3.0.9
Severity: Normal Keywords: 030-backport tor-sr
Cc: asn Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by dgoulet)

Compiled tor from source, tried both the Gitlab and the tarball from this site, both 0.3.0.9. When I try to run tor it exits at ~80% with the following error message

Machine : Linux t1 2.6.32-042stab120.5 #1 SMP Tue Oct 25 22:31:12 MSK 2016 x86_64 x86_64 x86_64 GNU/Linux

OpenSSL: tor-0.3.0.9# openssl version
OpenSSL 1.0.1f 6 Jan 2014

Jul 11 02:59:45.000 [err] tor_assertion_failed_(): Bug: src/or/shared_random.c:922: sr_generate_our_commit: Assertion my_rsa_cert failed; aborting. (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug: Assertion my_rsa_cert failed in sr_generate_our_commit at src/or/shared_random.c:922. Stack trace: (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(log_backtrace+0x42) [0x7f1b32ea7d02] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(tor_assertion_failed_+0x94) [0x7f1b32ebf4b4] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(sr_generate_our_commit+0x40e) [0x7f1b32db013e] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(sr_state_update+0x245) [0x7f1b32db2c55] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(sr_state_init+0x8c) [0x7f1b32db310c] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(do_main_loop+0x312) [0x7f1b32d9b832] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(tor_main+0x1c25) [0x7f1b32d9ee05] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(main+0x19) [0x7f1b32d97299] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f1b317c8f45] (on Tor 0.3.0.9 22b3bf094e327093)
Jul 11 02:59:45.000 [err] Bug:     tor(+0x462eb) [0x7f1b32d972eb] (on Tor 0.3.0.9 22b3bf094e327093)

Child Tickets

Change History (5)

comment:1 Changed 2 years ago by nickm

Cc: asn dgoulet added
Keywords: 030-backport tor-sr added
Milestone: Tor: 0.3.1.x-final

It's odd that we're hitting the sr_generate_our_commit code. What is in your torrc?

comment:2 Changed 2 years ago by dgoulet

Cc: dgoulet removed
Description: modified (diff)

(Small change in the description so we can read the stacktrace properly)

comment:3 Changed 2 years ago by dgoulet

Priority: MediumHigh
Status: newneeds_information

The sr_state_init() can *NOT* be reached without AuthoritativeDirectory 1 and V3AuthoritativeDirectory 1.

Furthermore, the assert() we are seeing here means that get_my_v3_authority_cert() sent back NULL meaning authority_key_certificate = NULL. This is set in init_keys() where we need authdir_mode_v3() to be true which is the same exact safeguard before the sr_init() call in main.c.

I've tried those two options with tor and I do get this warning and tor exits as it is suppose to do.

Jul 11 09:02:07.000 [err] We're configured as a V3 authority, but we were unable to load our v3 authority keys and certificate! Use tor-gencert to generate them. Dying.

So yeah two things, your torrc options would be very important to have and then if you can any prior logging.

comment:4 Changed 2 years ago by dgoulet

Resolution: duplicate
Status: needs_informationclosed

Oh wait... I didn't realize that we fixed an assert crash for BridgeAuthority and SR in 031 but not in 030. See commit 931948ac6ad0c6f5327fd3c212ce6fe241a071f1 released in 031.

#21586 is what you are hitting. It has not been backported to 030 because users in general don't use the Authoritative options except in testing.

So removing any kind of "Authoritative" options will fix this.

Closing and marking as duplicate.

comment:5 in reply to:  4 Changed 2 years ago by ram

I was using an old torrc from before - that must be it, thanks!

Replying to dgoulet:

Oh wait... I didn't realize that we fixed an assert crash for BridgeAuthority and SR in 031 but not in 030. See commit 931948ac6ad0c6f5327fd3c212ce6fe241a071f1 released in 031.

#21586 is what you are hitting. It has not been backported to 030 because users in general don't use the Authoritative options except in testing.

So removing any kind of "Authoritative" options will fix this.

Closing and marking as duplicate.

Note: See TracTickets for help on using tickets.