[tor-relays] tor_bug_occured_(): This line should not have been reached

[David Goulet]

On 07 Jul (01:16:07), Michael Gerstacker wrote:
> Hey guys,
> 
> my relay
> 79E683340B80676DCEB029E48FBD36BC66EBDA1E
> told me:
> 
> 
> Jul 06 15:22:34.000 [notice] DoS mitigation since startup: 0 circuits
> killed with too many cells. 150515 circuits rejected, 16 marked addresses.
> 0 connections closed. 104 single hop clients refused.
> 
> Jul 06 16:23:25.000 [warn] tor_bug_occurred_(): Bug:
> ../src/core/or/channeltls.c:1111: channel_tls_handle_cell: This line should
> not have been reached. (Future instances of this warning will be silenced.)
> (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug: Line unexpectedly reached at
> channel_tls_handle_cell at ../src/core/or/channeltls.c:1111. Stack trace:
> (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(log_backtrace_impl+0x46)
> [0x562903c4faa6] (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(tor_bug_occurred_+0xc0)
> [0x562903c4b1c0] (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:
> /usr/bin/tor(channel_tls_handle_cell+0x49a) [0x562903ad571a] (on Tor
> 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(+0x9a16a) [0x562903af916a]
> (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:
> /usr/bin/tor(connection_handle_read+0x99d) [0x562903ac318d] (on Tor 0.3.5.8
> )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(+0x69ebe) [0x562903ac8ebe]
> (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:
> /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x229ba) [0x7f469cdbf9ba] (on
> Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:
> /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7)
> [0x7f469cdc0537] (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(do_main_loop+0xb0)
> [0x562903aca290] (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(tor_run_main+0x10e5)
> [0x562903ab80d5] (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(tor_main+0x3a)
> [0x562903ab530a] (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(main+0x19)
> [0x562903ab4ec9] (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f469c6a109b]
> (on Tor 0.3.5.8 )
> 
> Jul 06 16:23:25.000 [warn] Bug:     /usr/bin/tor(_start+0x2a)
> [0x562903ab4f1a] (on Tor 0.3.5.8 )
> 
> Jul 06 21:22:34.000 [notice] Heartbeat: Tor's uptime is 12 days 6:00 hours,
> with 5113 circuits open. I've sent 2802.42 GB and received 2781.10 GB.
> 
> Jul 06 21:22:34.000 [notice] Circuit handshake stats since last time:
> 13801/13801 TAP, 169020/169020 NTor.
> 
> 
> Its anyway a little bit strange because this is the only relay i have which
> never deleted his logfiles since i set it up and where i can not change the
> language of the operating system.
> I think its related to the host system but i never really thought about
> because it seems to work fine.
> 
> Something i should do now?

Nothing much to do here. Fortunately, the relay recovers after that.

I've created this ticket about this issue:
https://trac.torproject.org/projects/tor/ticket/31107

I haven't had time to look into this just yet. However, thanks for the report!

Cheers!
David

-- 
fE4jqrcBXUKBv6iyHwOJ9X/7UU0f02CVPufALtF1L74=
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20190708/398f4fc7/attachment.sig>