Failed to find node for hop #1 of our path. Discarding this circuit

Been two days in a row with git master (033-alpha), when I boot up my computer and tor starts and fails to bootstrap. It takes around 8 minutes before it finally work.

The particularity I have with my tor client is that I pin my EntryNodes with one specific Guard for testing purposes and I stumbled on this issue.

Attached to the ticket are the info logs from the start of tor up to the 100% bootstrap.

changed milestone to %Tor: unspecified

added 034-removed-20180328 034-triage-20180328 040-deferred-20190220 bootstrap component::core tor/tor milestone::Tor: unspecified parent::26310 priority::medium severity::normal status::new tor-client type::defect labels

Trac:
info-ticket.log

Brief log analysis: Seems like we failed to fetch a consensus diff 4 times over 10 mins from different fallback dirs:

Nov 15 09:34:57.000 [info] directory_send_command(): Downloading consensus from 198.199.64.217:443 using 
/tor/status-vote/current/consensus-microdesc/0232AF+14C131+23D15D+27102B+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z
Nov 15 09:35:57.000 [info] directory_send_command(): Downloading consensus from 51.254.246.203:9001 using 
/tor/status-vote/current/consensus-microdesc/0232AF+14C131+23D15D+27102B+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z
Nov 15 09:38:57.000 [info] directory_send_command(): Downloading consensus from 109.163.234.5:443 using 
/tor/status-vote/current/consensus-microdesc/0232AF+14C131+23D15D+27102B+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z
Nov 15 09:41:57.000 [info] directory_send_command(): Downloading consensus from 212.129.62.232:443 using 
/tor/status-vote/current/consensus-microdesc/0232AF+14C131+23D15D+27102B+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z

We got the diff the last time, but during those 10 mins we refused to populate our guard list because we had no live consensus:

Nov 15 09:34:57.000 [info] entry_guards_expand_sample(): Not expanding the sample guard set; we have no live consensus.

I think there are two questions here: a) Why did we fail to fetch the consensus diff for 10mins? b) Why did we wait for a live consensus to populate guard list? Why not a reasonably live one? i think the answer lies in #22400 (moved).

Trac:
Keywords: tor-client deleted, tor-client bootstrap s8-errors added
Cc: N/A to catalyst
Sponsor: N/A to Sponsor8-can

I just want to point out that this thing is still really annoying... I get that every week where my tor client can't do anything because I have a pinned EntryNodes but seems no descriptor for it.

These feature and bugfix tickets have no patches. The earliest they will get done is 0.3.4.

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.4.x-final

Trac:
Keywords: tor-client bootstrap s8-errors deleted, tor-client, s8-errors, bootstrap, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: unspecified

We think the guard part of this is fixed by #24661 (moved), and the consensus diff part will be fixed in #26310 (moved).

Trac:
Parent: N/A to #26310 (moved)
Milestone: Tor: unspecified to Tor: 0.4.0.x-final

Trac:
Sponsor: Sponsor8-can to N/A
Keywords: s8-errors deleted, N/A added

Deferring 51 tickets from 0.4.0.x-final. Tagging them with 040-deferred-20190220 for visibility. These are the tickets that did not get 040-must, 040-can, or tor-ci.

Trac:
Keywords: N/A deleted, 040-deferred-20190220 added
Milestone: Tor: 0.4.0.x-final to Tor: unspecified

mentioned in issue #28733 (moved)

moved to tpo/core/tor#24300 (closed)