Opened 7 months ago

Closed 5 months ago

#33686 closed defect (user disappeared)

Tor 0.4.2.7 wont get past bootstrap phase with Sandbox 1 enabled

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version: Tor: 0.4.2.7
Severity: Normal Keywords: tor-sandbox, 035-backport, 041-backport, 042-backport, 043-backport
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I get this output from the terminal only when Sandbox 1 is enabled and it did not happen on earlier versions:

Mar 21 21:07:21.000 [notice] Bootstrapped 0% (starting): Starting
Mar 21 21:10:10.000 [notice] Starting with guard context "default"
Mar 21 21:10:10.000 [warn] tor_bug_occurred_(): Bug: src/lib/evloop/workqueue.c:353: workerthread_new: This line should not have been reached. (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: Tor 0.4.2.7: Line unexpectedly reached at workerthread_new at src/lib/evloop/workqueue.c:353. Stack trace: (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(log_backtrace_impl+0x47) [0x600404] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_bug_occurred_+0xa9) [0x5fcea2] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(threadpool_new+0x12b) [0x5ae6b0] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(cpu_init+0x59) [0x4be66e] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(run_tor_main_loop+0x9f) [0x4b3064] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_run_main+0xb85) [0x4b3f16] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_main+0x23) [0x4b1f98] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(main+0x13) [0x4b1c24] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: /lib/arm-linux-gnueabihf/libc.so.6(libc_start_main+0x97) [0xb694b524] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [err] Can't launch worker thread.
Mar 21 21:10:10.000 [warn] tor_bug_occurred_(): Bug: src/lib/evloop/workqueue.c:519: threadpool_start_threads: This line should not have been reached. (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: Tor 0.4.2.7: Line unexpectedly reached at threadpool_start_threads at src/lib/evloop/workqueue.c:519. Stack trace: (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(log_backtrace_impl+0x47) [0x600404] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_bug_occurred_+0xa9) [0x5fcea2] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(threadpool_new+0x15b) [0x5ae6e0] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(cpu_init+0x59) [0x4be66e] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(run_tor_main_loop+0x9f) [0x4b3064] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_run_main+0xb85) [0x4b3f16] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_main+0x23) [0x4b1f98] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(main+0x13) [0x4b1c24] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: /lib/arm-linux-gnueabihf/libc.so.6(
libc_start_main+0x97) [0xb694b524] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] tor_bug_occurred_(): Bug: src/lib/evloop/workqueue.c:563: threadpool_new: This line should not have been reached. (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: Tor 0.4.2.7: Line unexpectedly reached at threadpool_new at src/lib/evloop/workqueue.c:563. Stack trace: (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(log_backtrace_impl+0x47) [0x600404] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_bug_occurred_+0xa9) [0x5fcea2] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(threadpool_new+0x183) [0x5ae708] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(cpu_init+0x59) [0x4be66e] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(run_tor_main_loop+0x9f) [0x4b3064] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_run_main+0xb85) [0x4b3f16] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_main+0x23) [0x4b1f98] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(main+0x13) [0x4b1c24] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: /lib/arm-linux-gnueabihf/libc.so.6(libc_start_main+0x97) [0xb694b524] (on Tor 0.4.2.7 )

============================================================ T= 1584825010
Tor 0.4.2.7 died: Caught signal 11
tor(+0x19631a)[0x60031a]
tor(threadpool_register_reply_event+0x19)[0x5ae80e]
tor(threadpool_register_reply_event+0x19)[0x5ae80e]
tor(cpu_init+0x61)[0x4be676]
tor(run_tor_main_loop+0x9f)[0x4b3064]
tor(tor_run_main+0xb85)[0x4b3f16]
tor(tor_main+0x23)[0x4b1f98]
tor(main+0x13)[0x4b1c24]
/lib/arm-linux-gnueabihf/libc.so.6(libc_start_main+0x97)[0xb694b524]

[1]+ Illegal instruction tor -f torrc

Child Tickets

Change History (8)

comment:1 Changed 7 months ago by nickm

To confirm: you've tried this with the same version of libseccomp and the same kernel and Tor 0.4.2.6, and you don't get the same error?

comment:2 Changed 7 months ago by nickm

If you confirm that -- what linux distribution do you have, what libc, and what version of libseccomp?

comment:3 Changed 7 months ago by cypherpunks

libseccomp2 is already the newest version (2.3.3-4)

ldd (Debian GLIBC 2.28-10) 2.28

Mar 22 03:22:32.271 [notice] Tor 0.4.2.6 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.

Mar 22 03:23:18.000 [warn] This version of Tor was built without support for sandboxing. To build with support for sandboxing on Linux, you must have libseccomp and its necessary header files (e.g. seccomp.h).

It looks like sandboxing never worked on my system but with version 0.4.2.6 it handles this gracefully which is why i never noticed before that it was a problem. I must have just always skipped over that warn message. With tor 0.4.2.7 it crashes instead of giving this warning.
When i built tor i just used the default options by running the configure script then using make. I did not specifically enable libseccomp, maybe that is the problem.

comment:4 Changed 7 months ago by cypherpunks

yes it is all the same version of everything.

comment:5 Changed 7 months ago by dgoulet

Milestone: Tor: 0.4.4.x-final

comment:6 Changed 7 months ago by teor

Keywords: tor-sandbox added

Your 0.4.2.6 was not built with sandboxing enabled.
What about building 0.4.2.6 with sandboxing enabled?

comment:7 Changed 7 months ago by teor

Keywords: 035-backport 041-backport 042-backport 043-backport added

comment:8 Changed 5 months ago by nickm

Resolution: user disappeared
Status: newclosed

no response in 2 months; closing :(

Note: See TracTickets for help on using tickets.