[tor-bugs] #13137 [Onionoo]: Historical data
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Sep 17 09:20:15 UTC 2014
#13137: Historical data
---------------------------+-----------------
Reporter: Sebastian | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Onionoo | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
---------------------------+-----------------
Comment (by Sebastian):
It's really hard for me to come up with an exact usecase. Recently, I
aimlessly scrolled through the consensus-health page, and noticed gabelmoo
wasn't voting running for a bunch of relays. So I tried check its log, but
it logged it found them reachable. So I thought maybe it was a fluke this
hour, and waited for the next hour. Hrm, same thing. I then downloaded old
consensuses to see if this was a recent development or something that came
up a longer time ago, learned it was somewhat recent (which was good,
because I try to take good care of gabelmoo and hence scroll through
consensus-health every now and then). Then after some more poking I
realized something all those relays had in common: ipv6. I then noticed
that my upstream had broken ipv6 on the host. I didn't have proper
monitoring in place for that, but without something like consensus-health
I'd still not vote Running on these relays. If I could click on the page,
and it'd pull up the descriptors for the relays and show me the flags and
when I voted what for them, it could help track down what I changed to
cause an issue.
Another instance is when a relay operator complains because they aren't in
the consensus, I look at consensus-health to see who is voting what, and
try to figure out why. It just gives a quick overview for a relay. For
that, it'd be good if it would show ip information, too, so I could search
for that (in this case, I had ip address and relay nickname, and
fortunately the nickname was unique enough to identify the relay).
A third example is my work to get rid of the Naming flag, and redo the
BadExiting/Rejecting/Valid-voting stuff. I tested a version of my patch,
and it only voted 10/22 relays as BadExit, so obviously some where
missing. Trouble was, none of the missing relays made it into the
consensus, they were just in the votes. Their nicknames were "default", so
searching for that didn't help either. After a bit, arma noticed that
these were syrian and iranian relays. This, too, could've been much
quicker resolved if I could've clicked on the relay, it would've pulled up
the page with all the information about it (this time including country).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13137#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list