[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #33663 [Metrics/Consensus Health]: Check checktest.py related errors shown by our network-health scanners
#33663: Check checktest.py related errors shown by our network-health scanners
-------------------------------------------------+-------------------------
Reporter: gk | Owner: gk
Type: task | Status:
| assigned
Priority: Medium | Milestone:
Component: Metrics/Consensus Health | Version:
Severity: Normal | Resolution:
Keywords: network-health, network-health- | Actual Points:
roadmap-2020Q1, GeorgKoppen202003 |
Parent ID: #33180 | Points: 0.5
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by gk):
Replying to [comment:2 irl]:
> The issue is not whether the exit is able to resolve it, but whether the
exit is able to exit to it. Exits need to be able to make exit connections
to 116.202.120.181:443. This is a fundamental limitation of the current
exit scanner and would need redesign to do differently.
Thanks, yes, being able to resolve `check.torproject.org` is just a
necessary requirement but not sufficient. I should have been clearer,
sorry for that. So, the node can make an exit connection to
`check.torproject.org` as it gets JSON back and complaining afterwards
that it got `"IsTor":false`. Now, there are cases where this can happen,
e.g. as the exitscanner might have a different consensus containing relays
the check test script does not have once it is run and vice versa but
that's usually not causing a permanent failure as in this case.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33663#comment:3>
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