You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Tor is dormant and txtorcon connects and tries to build a circuit, this may fail with 552 no descriptor for X because Tor still fetches enough consensus to know about new/current relays, but doesn't fetch (micro)descriptors if it is dormant.
GETINFO dormant will tell us if Tor is dormant. So: if there's a .build call in progress, and we get a 552, and Tor is dormant, we should wake it up. Recommended way to do this is to resolve a DNS or try to connect to soemthing (e.g. we could do a lookup for torproject.org via SOCKS).
Thanks to arma and teor on #tor-dev for discussion
The text was updated successfully, but these errors were encountered:
If Tor is dormant and txtorcon connects and tries to build a circuit, this may fail with
552 no descriptor for X
because Tor still fetches enough consensus to know about new/current relays, but doesn't fetch (micro)descriptors if it is dormant.GETINFO dormant
will tell us if Tor is dormant. So: if there's a.build
call in progress, and we get a 552, and Tor is dormant, we should wake it up. Recommended way to do this is to resolve a DNS or try to connect to soemthing (e.g. we could do a lookup fortorproject.org
via SOCKS).Thanks to arma and teor on
#tor-dev
for discussionThe text was updated successfully, but these errors were encountered: