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

Re: [tor-bugs] #22032 [Core Tor/Tor]: [warn] Hidden service fn3xxgdv5skhtza2 launched 0 intro points in the last 3193 seconds (delayed). Intro circuit launches are limited to 8 per 300 seconds.



#22032: [warn] Hidden service fn3xxgdv5skhtza2 launched 0 intro points in the last
3193 seconds (delayed). Intro circuit launches are limited to 8 per 300
seconds.
--------------------------+------------------------------------
 Reporter:  arma          |          Owner:
     Type:  defect        |         Status:  needs_review
 Priority:  Medium        |      Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  tor-hs        |  Actual Points:
Parent ID:                |         Points:  0.1
 Reviewer:                |        Sponsor:  SponsorR-can
--------------------------+------------------------------------
Changes (by dgoulet):

 * status:  new => needs_review
 * points:   => 0.1


Comment:

 Ok scratch the above. So the issue is that we dump logs at every 5 minutes
 at info level now (introduced in c34411d9cb not yet released). That is
 fine.

 However, `rend_log_intro_limit()` has this snippet that upgrades the log
 to warning:

 {{{
   int exceeded_elapsed = (intro_period_elapsed > INTRO_CIRC_RETRY_PERIOD +
                           INTRO_CIRC_RETRY_PERIOD_SLOP);
   if (exceeded_elapsed) {
     severity = LOG_WARN;
   }
 }}}

 We shouldn't do that if we have not exceeded the limit of circuit creation
 in the first place (`exceeded_limit`). Exceeding the elapsed retry period
 is fine and actually expected sometimes because "network down" for
 instance.

 See branch `bug22032_031_01`.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22032#comment:3>
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