[tor-bugs] #25733 [Core Tor/Tor]: Bug: Could not determine largest build time (0). Xm is 3925ms and we've abandoned 999 out of 1000 circuits.

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Apr 6 20:55:01 UTC 2018


#25733: Bug: Could not determine largest build time (0). Xm is 3925ms and we've
abandoned 999 out of 1000 circuits.
------------------------------+---------------------------
     Reporter:  cstest        |      Owner:  (none)
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:
    Component:  Core Tor/Tor  |    Version:  Tor: 0.3.2.10
     Severity:  Normal        |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |   Reviewer:
      Sponsor:                |
------------------------------+---------------------------
 Server running couple of hundred HS domains. Tor crashed. One spammer is
 trying simple DDoS.



 Apr 06 20:36:28.000 [notice] Received reload signal (hup). Reloading
 config and resetting internal state.
 Apr 06 20:36:28.000 [notice] Read configuration file
 "-------------------".
 Apr 06 20:36:28.000 [notice] Tor 0.3.2.10 (git-0edaa32732ec8930) opening
 log file.
 Apr 06 20:36:42.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Apr 06 20:36:42.000 [warn] Error launching circuit to node
 $F0F5074A6DADD3DC22E1FAA18FD6D89C-------- at --------- for service
 ---------------.
 Apr 06 20:36:56.000 [warn] Your Guard remedy
 ($3FEBFB6A491D30CACC2C2995EDB41717A6F94E95) is failing a very large amount
 of circuits. Most likely this means the Tor network is overloaded, but it
 could$
 Apr 06 20:36:59.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Apr 06 20:37:26.000 [warn] Your Guard AlienZone
 ($80392DC1522E647C56457CEBA58DD84CC56AEC44) is failing a very large amount
 of circuits. Most likely this means the Tor network is overloaded, but it
 co$
 Apr 06 20:37:29.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Apr 06 20:37:29.000 [warn] Error launching circuit to node
 $9AEF164F5BE5618509C9E60----------- at ---------------- for service
 ---------------------------.
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 996
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 997
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 998
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 ........
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 3925ms and we've abandoned 999
 out of 1000 circuits. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] tor_assertion_failed_(): Bug:
 ../src/or/circuitstats.c:772: circuit_build_times_get_xm: Assertion
 bin_counts > 0 failed; aborting. (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug: Assertion bin_counts > 0 failed in
 circuit_build_times_get_xm at ../src/or/circuitstats.c:772. Stack trace:
 (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /usr/sbin/tor(log_backtrace+0x43)
 [0x55ff6c113313] (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:
 /usr/sbin/tor(tor_assertion_failed_+0x8d) [0x55ff6c12e54d] (on Tor
 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:
 /usr/sbin/tor(circuit_build_times_set_timeout+0x83e) [0x55ff6c0760be] (on
 Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:
 /usr/sbin/tor(circuit_expire_building+0x1012) [0x55ff6c07a5b2] (on Tor
 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /usr/sbin/tor(+0x52bd7)
 [0x55ff6bfdfbd7] (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /usr/lib/x86_64-linux-
 gnu/libevent-2.1.so.6(+0x1f6aa) [0x7faafc9836aa] (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /usr/lib/x86_64-linux-
 gnu/libevent-2.1.so.6(event_base_loop+0x5a7) [0x7faafc984227] (on Tor
 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /usr/sbin/tor(do_main_loop+0x28d)
 [0x55ff6bfe085d] (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /usr/sbin/tor(tor_main+0xe1d)
 [0x55ff6bfe367d] (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /usr/sbin/tor(main+0x19)
 [0x55ff6bfdc0a9] (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /lib/x86_64-linux-
 gnu/libc.so.6(__libc_start_main+0xf1) [0x7faafb18b1c1] (on Tor 0.3.2.10 )
 Apr 06 20:37:49.000 [err] Bug:     /usr/sbin/tor(_start+0x2a)
 [0x55ff6bfdc0fa] (on Tor 0.3.2.10 )

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25733>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list