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

Re: [tor-bugs] #24991 [Core Tor/Tor]: SingleOnion claims "missing descriptors for 1/2 of our primary entry guards", has no guards, makes no sense

#24991: SingleOnion claims "missing descriptors for 1/2 of our primary entry
guards", has no guards, makes no sense
-------------------------------------------------+-------------------------
 Reporter:  alecmuffett                          |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  unspecified
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.3.4.1-alpha
 Severity:  Minor                                |     Resolution:
 Keywords:  single-onion, guards, logging,       |  Actual Points:
  easy, 034-triage-20180328,                     |
  034-removed-20180328                           |
Parent ID:  #23863                               |         Points:  0.5
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by starlight):

 * version:  Tor: 0.3.2.9 => Tor: 0.3.4.1-alpha


Comment:

 Seeing this with 0.3.4.1-alpha on a guard relay that has no client
 activity.  Something seems wrong about it because the shortage of
 descriptors is minuscule yet the message indicates a guard appears in the
 missing set.  Performed a DROPGUARDS thinking one of the guards was bum
 somehow, and the message came back the next day with the fresh set.  I
 wonder if this is a bug in the new differential descriptor logic; why
 would 50 relays go missing every day as an exceptional event?

 {{{
 DownloadExtraInfo 1
 }}}

 Removed cached-* and diff-cache/* before start.



 {{{
 Tor 0.3.4.1-alpha (git-deb8970a29ef7427) running on Linux with Libevent
 x.x.x, OpenSSL x.x.x, Zlib x.x.x, Liblzma x.x.x, and Libzstd x.x.x.
 Bootstrapped 0%: Starting
 Starting with guard context "default"
 Bootstrapped 10%: Finishing handshake with directory server
 I learned some more directory information, but not enough to build a
 circuit: We have no usable consensus.
 I learned some more directory information, but not enough to build a
 circuit: We have no usable consensus.
 Bootstrapped 45%: Asking for relay descriptors
 I learned some more directory information, but not enough to build a
 circuit: We need more microdescriptors: we have 0/6493, and can only build
 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of
 exit bw = 0% of path bw.)
 I learned some more directory information, but not enough to build a
 circuit: We need more microdescriptors: we have 0/6493, and can only build
 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of
 exit bw = 0% of path bw.)
 Bootstrapped 50%: Loading relay descriptors
 Bootstrapped 55%: Loading relay descriptors
 Bootstrapped 60%: Loading relay descriptors
 Bootstrapped 65%: Loading relay descriptors
 Bootstrapped 70%: Loading relay descriptors
 Problem bootstrapping. Stuck at 73%: Loading relay descriptors. (No route
 to host; NOROUTE; count 1; recommendation warn; host X at x.x.x.x:x)
 Bootstrapped 75%: Loading relay descriptors
 Bootstrapped 80%: Connecting to the Tor network
 Bootstrapped 85%: Finishing handshake with first hop
 Bootstrapped 90%: Establishing a Tor circuit
 Tor has successfully opened a circuit. Looks like client functionality is
 working.
 Bootstrapped 100%: Done
 Self-testing indicates your DirPort is reachable from the outside.
 Excellent. Publishing server descriptor.
 Performing bandwidth self-test...done.
 Heartbeat: Tor's uptime is 6:00 hours,
 Heartbeat: Tor's uptime is 12:00 hours,
 Heartbeat: Tor's uptime is 18:00 hours,
 Heartbeat: Tor's uptime is 1 day 0:00 hours,
 Heartbeat: Tor's uptime is 1 day 6:00 hours,
 Heartbeat: Tor's uptime is 1 day 12:00 hours,
 Heartbeat: Tor's uptime is 1 day 18:00 hours,
 Heartbeat: Tor's uptime is 2 days 0:00 hours,
 Heartbeat: Tor's uptime is 2 days 6:00 hours,
 Heartbeat: Tor's uptime is 2 days 12:00 hours,
 Heartbeat: Tor's uptime is 2 days 18:00 hours,
 Heartbeat: Tor's uptime is 3 days 0:00 hours,
 Heartbeat: Tor's uptime is 3 days 6:00 hours,
 Heartbeat: Tor's uptime is 3 days 12:00 hours,
 Heartbeat: Tor's uptime is 3 days 18:00 hours,
 Heartbeat: Tor's uptime is 4 days 0:00 hours,
 Channel padding timeout scheduled 209531ms in the past.
 Heartbeat: Tor's uptime is 4 days 6:00 hours,
 Heartbeat: Tor's uptime is 4 days 12:00 hours,
 Heartbeat: Tor's uptime is 4 days 18:00 hours,
 Heartbeat: Tor's uptime is 5 days 0:00 hours,
 Heartbeat: Tor's uptime is 5 days 6:00 hours,
 Our directory information is no longer up-to-date enough to build
 circuits: We're missing descriptors for 1/2 of our primary entry guards
 (total microdescriptors: 6346/6383).
 I learned some more directory information, but not enough to build a
 circuit: We're missing descriptors for 1/2 of our primary entry guards
 (total microdescriptors: 6346/6383).
 We now have enough directory information to build circuits.
 Heartbeat: Tor's uptime is 5 days 12:00 hours,
 Heartbeat: Tor's uptime is 5 days 18:00 hours,
 Heartbeat: Tor's uptime is 6 days 0:00 hours,
 Heartbeat: Tor's uptime is 6 days 6:00 hours,
 Heartbeat: Tor's uptime is 6 days 12:00 hours,
 Heartbeat: Tor's uptime is 6 days 18:00 hours,
 Heartbeat: Tor's uptime is 7 days 0:00 hours,
 Heartbeat: Tor's uptime is 7 days 6:00 hours,
 Heartbeat: Tor's uptime is 7 days 12:00 hours,
 Heartbeat: Tor's uptime is 7 days 18:00 hours,
 Our directory information is no longer up-to-date enough to build
 circuits: We're missing descriptors for 1/2 of our primary entry guards
 (total microdescriptors: 6307/6352).
 I learned some more directory information, but not enough to build a
 circuit: We're missing descriptors for 1/2 of our primary entry guards
 (total microdescriptors: 6307/6352).
 We now have enough directory information to build circuits.

 DROPGUARDS is dangerous; make sure you understand the risks before using
 it. It may be removed in a future version of Tor.
 Starting with guard context "default"

 Heartbeat: Tor's uptime is 8 days 0:00 hours,
 Heartbeat: Tor's uptime is 8 days 6:00 hours,
 Heartbeat: Tor's uptime is 8 days 12:00 hours,
 Heartbeat: Tor's uptime is 8 days 18:00 hours,
 Our directory information is no longer up-to-date enough to build
 circuits: We're missing descriptors for 1/2 of our primary entry guards
 (total microdescriptors: 6317/6353).
 I learned some more directory information, but not enough to build a
 circuit: We're missing descriptors for 1/2 of our primary entry guards
 (total microdescriptors: 6317/6353).
 We now have enough directory information to build circuits.
 }}}

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