Your message dated Tue, 11 Sep 2018 12:30:13 +0000 with message-id <[email protected]> and subject line Re: Bug#878172: tor_bug_occurred_(): Bug: ../src/common/compress.c:576: tor_compress_process: Non-fatal assertion !((rv == TOR_COMPRESS_OK)... has caused the Debian Bug report #878172, regarding tor_bug_occurred_(): Bug: ../src/common/compress.c:576: tor_compress_process: Non-fatal assertion !((rv == TOR_COMPRESS_OK)... to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 878172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878172 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: tor Version: 0.3.1.7-1~bpo9+1 Severity: normal Dear Maintainer, I run a tor relay/exit running on stretch and I upgraded to the stretch-backports 0.3.1.7-1~bpo9+1 version that recently became available. About every two hours the following is logged: Oct 10 09:30:20 ghatanothoa Tor[30872]: tor_bug_occurred_(): Bug: ../src/common/compress.c:576: tor_compress_process: Non-fatal assertion !((rv == TOR_COMPRESS_OK) && *in_len == in_len_orig && *out_len == out_len_orig) failed. (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: Non-fatal assertion !((rv == TOR_COMPRESS_OK) && *in_len == in_len_orig && *out_len == out_len_orig) failed in tor_compress_process at ../src/common/compress.c:576. Stack trace: (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(log_backtrace+0x44) [0x5571c1ed4194] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(tor_bug_occurred_+0xb9) [0x5571c1eed029] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(tor_compress_process+0x135) [0x5571c1ef5fa5] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(+0x18e171) [0x5571c1ef6171] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(tor_uncompress+0x31) [0x5571c1ef6631] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(connection_dir_reached_eof+0x118c) [0x5571c1e9866c] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(+0x1089bc) [0x5571c1e709bc] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(+0x4d85e) [0x5571c1db585e] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x6a0) [0x7f5d4ca3a5a0] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(do_main_loop+0x29d) [0x5571c1db698d] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(tor_main+0x1c35) [0x5571c1dba4d5] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(main+0x19) [0x5571c1db2189] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f5d4b49c2b1] (on Tor 0.3.1.7 ) Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(_start+0x2a) [0x5571c1db21da] (on Tor 0.3.1.7 ) Oct 10 09:37:27 ghatanothoa Tor[30872]: Tried to establish rendezvous on non-OR circuit with purpose Acting as rendevous (pending) It looks like upstream bug 22719: https://trac.torproject.org/projects/tor/ticket/22719 I have the same package running on several other hosts that are not relays that never see this error. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (701, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tor depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii libc6 2.24-11+deb9u1 ii libevent-2.0-5 2.0.21-stable-3 ii liblzma5 5.2.2-1.2+b1 ii libseccomp2 2.3.1-2.1 ii libssl1.1 1.1.0f-3 ii libsystemd0 232-25+deb9u1 ii libzstd1 1.1.2-1 ii lsb-base 9.20161125 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages tor recommends: ii logrotate 3.11.0-0.1 ii tor-geoipdb 0.2.9.12-1 ii torsocks 2.2.0-1+deb9u1 Versions of packages tor suggests: pn apparmor-utils <none> pn mixmaster <none> pn obfs4proxy <none> pn obfsproxy <none> pn socat <none> ii tor-arm 1.4.5.0-1.1 pn torbrowser-launcher <none> -- Configuration Files: /etc/tor/torrc changed [not included] -- no debconf information -- Gerald Turner <[email protected]> Encrypted mail preferred! OpenPGP: 4096R / CA89 B27A 30FA 66C5 1B80 3858 EC94 2276 FDB8 716D
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Version: 0.3.1.4-alpha this was fixed a long time ago: Changes in version 0.3.1.4-alpha - 2017-06-29 - When spooling compressed data to an output buffer, don't try to spool more data when there is no more data to spool and we are not trying to flush the input. Previously, we would sometimes launch compression requests with nothing to do, which interferes with our 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `- https://www.debian.org/
--- End Message ---
