Opened 4 months ago

Closed 3 months ago

#27040 closed defect (fixed)

[warn] We don't have a consensus, so we can't perform v2 rendezvous operations.

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.3.5.x-final
Component: Core Tor/Tor Version:
Severity: Minor Keywords: fast-fix easy
Cc: asn Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Start your Tor, and while it's bootstrapping, make an onion service request. (In my case I started 'apt-get update' which uses the apt-transport trick to make it use my Tor.)

Now I have in my logs:

Jul 30 20:27:11.890 [notice] Bootstrapped 25%: Loading networkstatus consensus
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.286 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.286 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.379 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.379 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.384 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.384 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.385 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.385 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:58.498 [notice] Bootstrapped 45%: Asking for relay descriptors

I think maybe it shouldn't warn like that if it hasn't bootstrapped yet? Or, is there some specific value to warning there?

Child Tickets

Change History (5)

comment:1 Changed 4 months ago by asn

Yes, I think we can safely demote that log message to info.

BTW, does the request proceeds after the bootstrap completes, or do you need to do the request again?

comment:2 Changed 4 months ago by arma

I think the request proceeded.

Wouldn't it be cool to have a unit test (or maybe this is more like a chutney test) to verify that it does work, and keeps working?

comment:3 Changed 4 months ago by nickm

Keywords: fast-fix easy 034-backport added
Milestone: Tor: 0.3.5.x-final

comment:4 Changed 3 months ago by dgoulet

Cc: dgoulet removed
Keywords: 034-backport removed
Status: newmerge_ready

See branch: ticket27040_035_01.

Trivial fix. We can't backport such a thing imo... Doesn't fall under our backport rules. If I'm wrong, great, put back the keyword :).

comment:5 Changed 3 months ago by nickm

Resolution: fixed
Status: merge_readyclosed

merged!

Note: See TracTickets for help on using tickets.