[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #16013 [Tor]: Assertion ENTRY_TO_CONN(conn)->state == AP_CONN_STATE_CIRCUIT_WAIT failed in circuit_get_open_circ_or_launch at circuituse.c:1835

#16013: Assertion ENTRY_TO_CONN(conn)->state == AP_CONN_STATE_CIRCUIT_WAIT failed
in circuit_get_open_circ_or_launch at circuituse.c:1835
-----------------------------+-------------------------------------
     Reporter:  cypherpunks  |      Owner:
         Type:  defect       |     Status:  needs_information
     Priority:  normal       |  Milestone:  Tor: 0.2.7.x-final
    Component:  Tor          |    Version:  Tor: unspecified
   Resolution:               |   Keywords:  regression 026-backport
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-------------------------------------

Comment (by starlight):

 Occurred to me how to characterize the
 traffic causing the problem and how it
 might be reproduced in test:

 Arrange for HS to fulfill 500 simultaneous
 requests for about 50-100KB, each via
 a separate connection.  Set up the
 client to use only two hard-coded
 guard nodes.  Maybe run this a couple
 of times and mix in other traffic.

 This seems to kick in some anti-DDOS
 measure on one or both guards and
 the messages

 Your Guard is failing more circuits than usual. . .
 We'd like to launch a circuit . .  . already have 128 . . . pending.
 Waiting until some finish.

 might appear. . .or might not appear.
 Might require NumCPUs be set 2 or greater, might not.
 Might require MaxClientCircuitsPending 128.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16013#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs