Re: [tor-bugs] #11156 [Tor]: "can't find a pluggable transport proxy" errors when obfsproxy started up

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#11156: "can't find a pluggable transport proxy" errors when obfsproxy started up
------------------------+------------------------------------------
     Reporter:  asn     |      Owner:
         Type:  defect  |     Status:  needs_review
     Priority:  normal  |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-pt tor-client, tbb-needs
Actual Points:          |  Parent ID:
       Points:          |
------------------------+------------------------------------------
Changes (by asn):

 * status:  needs_revision => needs_review


Comment:

 Replying to [comment:10 nickm]:
 > msg_out needs to be documented.
 >
 > QOI: msg_out should be set to NULL if we aren't delaying.
 >

 Fixed in fixup commit. Please check the branch again.

 > What limits the frequency with which we log this message?
 >

 Hm, you mean of the `log_notice()` in
 `update_router_have_minimum_dir_info()`? Good question.

 IIUC, we normally don't reach the `log_notice()` if we can't connect to
 bridges, because we don't have a consensus at all (it will fail the checks
 above).

 If we have a previously cached consensus, we might reach the
 `log_notice()` in which case it will print "Delaying dir fetches: PT
 proxies are still configuring" till the PTs finish configuring. This
 usually takes 2 `run_scheduled_events()` ticks, so that message should not
 appear too many times there. If you want, we can turn it to an info-level
 log if it's the PT case (and not the "no bridge descriptors known" case).

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