Opened 20 months ago

Last modified 5 weeks ago

#25957 needs_information defect

Tor 0.3.3.5-rc died: Caught signal 11

Reported by: Pine64ARMv8 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.3.3.5-rc
Severity: Normal Keywords: crash, openssl
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

from tor.log (tor server: devuan 8A00CE9638BDB4686B91F1F0B229DB3F8C9B8415):
.../...
Apr 28 00:58:53.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 9698 circuits open. I've sent 556.38 GB and received 553.75 GB.
Apr 28 00:58:53.000 [notice] Circuit handshake stats since last time: 21677/21677 TAP, 252349/252349 NTor.
Apr 28 00:58:53.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 1 v3 connections, and 16330 v4 connections; and received 36 v1 connections, 8546 v2 connections, 13955 v3 connections, and 12846 v4 connections.
Apr 28 00:58:53.000 [notice] DoS mitigation since startup: 0 circuits rejected, 0 marked addresses. 0 connections closed. 294 single hop clients refused.

============================================================ T= 1524879769
Tor 0.3.3.5-rc died: Caught signal 11
tor(+0x189059)[0x558d01f7c059]
/lib/x86_64-linux-gnu/libc.so.6(+0x791d5)[0x7f201753e1d5]
/lib/x86_64-linux-gnu/libc.so.6(+0x791d5)[0x7f201753e1d5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f201753ff64]
/usr/local/lib/libssl.so.1.1(+0x24f40)[0x7f2018ca4f40]
/usr/local/lib/libssl.so.1.1(+0x24b25)[0x7f2018ca4b25]
/usr/local/lib/libssl.so.1.1(+0x2baec)[0x7f2018cabaec]
/usr/local/lib/libssl.so.1.1(+0x374d0)[0x7f2018cb74d0]
/usr/local/lib/libssl.so.1.1(SSL_read+0x15)[0x7f2018cb76b5]
tor(tor_tls_read+0x52)[0x558d01fae7a2]
tor(buf_read_from_tls+0xac)[0x558d01fa01dc]
tor(+0x10b9e1)[0x558d01efe9e1]
tor(+0x5367e)[0x558d01e4667e]
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x6a0)[0x7f2018f1f5a0]
tor(do_main_loop+0x264)[0x558d01e47694]
tor(tor_run_main+0x275)[0x558d01e48c95]
tor(tor_main+0x3a)[0x558d01e422aa]
tor(main+0x19)[0x558d01e42019]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f20174e52e1]
tor(_start+0x2a)[0x558d01e4206a]

Child Tickets

Change History (10)

comment:1 Changed 20 months ago by teor

Keywords: crash openssl 033-must added; 0.3.3.5-rc died Caught signal 11 removed
Status: newneeds_information

Hi, can you tell us what version of OpenSSL tor was compiled with, and what version you have installed?
When Tor starts up, it logs a message containing this information, if the versions are different.

comment:2 Changed 20 months ago by cypherpunks

https://stackoverflow.com/questions/22051294/malloc-segmentation-fault

A SIGSEGV (segmentation fault) is firing in malloc is usually caused by heap corruption. Heap corruption does not cause a segmentation fault, so you would see that only when malloc tries to access there. The problem is that the code that creates the heap corruption could be in any point even far away from where the malloc is called. It is usually the next-block pointer inside the malloc that is changed by your heap corruption to an invalid address, so that when you call malloc an invalid pointer gets dereferenced and you get a segmentation fault.

comment:3 Changed 19 months ago by teor

Keywords: 033-must removed
Milestone: Tor: 0.3.3.x-finalTor: unspecified

We can't make progress on this issue until we have more information

comment:4 Changed 18 months ago by arma

Description: modified (diff)

comment:5 Changed 18 months ago by arma

See also #26311 for what might be a related bug.

comment:6 Changed 4 months ago by teor

From https://trac.torproject.org/projects/tor/ticket/30041#comment:13

i believe my issue is related. will this limit fix my bugs or should i open new ticket?

[warn] {BUG} Bug: Non-fatal assertion !(buf->datalen >= INT_MAX - at_most) failed in buf_read_from_tls at buffers_tls.c:73. (Stack trace not available) (on Tor 0.4.0.5 )

comment:7 in reply to:  1 Changed 4 months ago by teor

We are still waiting for this information on this ticket:

Replying to teor:

Hi, can you tell us what version of OpenSSL tor was compiled with, and what version you have installed?
When Tor starts up, it logs a message containing this information, if the versions are different.

comment:8 Changed 8 weeks ago by cypherpunks

Hi this is not my ticket, but i can give this info in my case where it just happened with latest stable again:

Oct 17 06:46:25.062 [notice] Tor 0.4.1.6 running on Windows 10 [or later] with Libevent 2.1.11-stable, OpenSSL 1.1.1, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.3.

...

Oct 17 07:08:48.000 [info] {APP} connection_edge_process_relay_cell(): 1632: end cell (closed normally) for stream 6445. Removing stream.
Oct 17 07:08:49.000 [info] {GENERAL} circuit_mark_for_close_(): Circuit 2112127911 (id: 151) marked for close at circuituse.c:1524 (orig reason: 9, new reason: 0)
Oct 17 07:08:49.000 [info] {GENERAL} circuit_mark_for_close_(): Circuit 2550036626 (id: 221) marked for close at circuituse.c:1524 (orig reason: 9, new reason: 0)
Oct 17 07:08:49.000 [info] {CIRC} circuit_free_(): Circuit 0 (id: 151) has been freed.
Oct 17 07:08:49.000 [info] {CIRC} circuit_free_(): Circuit 0 (id: 221) has been freed.
Oct 17 07:08:49.000 [info] {BTRACK} bto_status_rcvr(): ORCONN DELETE gid=135 status=3 reason=7
Oct 17 07:09:24.000 [warn] {BUG} tor_bug_occurred_(): Bug: buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion !(buf->datalen >= INT_MAX - at_most) failed. (Future instances of this warning will be silenced.) (on Tor 0.4.1.6 )
Oct 17 07:09:24.000 [warn] {BUG} Bug: Non-fatal assertion !(buf->datalen >= INT_MAX - at_most) failed in buf_read_from_tls at buffers_tls.c:73. (Stack trace not available) (on Tor 0.4.1.6 )

comment:9 in reply to:  8 ; Changed 7 weeks ago by arma

Replying to cypherpunks:

Hi this is not my ticket, but i can give this info in my case where it just happened with latest stable again:

Oct 17 07:09:24.000 [warn] {BUG} tor_bug_occurred_(): Bug: buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion !(buf->datalen >= INT_MAX - at_most) failed. (Future instances of this warning will be silenced.) (on Tor 0.4.1.6 )

That one looks like #32022.

Did your relay die with a segfault after writing that log message, or was the log message the extent of the problem?

comment:10 in reply to:  9 Changed 5 weeks ago by cypherpunks

Replying to arma:

Replying to cypherpunks:
Did your relay die with a segfault after writing that log message, or was the log message the extent of the problem?

It was running as relay node. This is correct. tor proccess didn't die. it kept running with high cpu usage on one core and didn't connect new socksport connections to destinations. last loglines found was as quoted above.

Note: See TracTickets for help on using tickets.