[tor-consensus-health] Consensus issues
Linus Nordberg
linus at nordberg.se
Wed Jun 26 20:41:57 UTC 2019
atagar at torproject.org wrote
Wed, 26 Jun 2019 20:22:46 +0000 (UTC):
> ERROR: Unable to retrieve the consensus from maatuska
> (http://171.25.193.9:443/tor/status-vote/current/consensus): timed out
Hi Damien,
maatuska was down for some 35h or so but is now up AFAICT. Any idea why
the consensus health machinery fails fetching the above document?
$ curl -v http://171.25.193.9:443/tor/status-vote/current/consensus > /dev/null
* Trying 171.25.193.9...
* TCP_NODELAY set
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 171.25.193.9 (171.25.193.9) port 443 (#0)
> GET /tor/status-vote/current/consensus HTTP/1.1
> Host: 171.25.193.9:443
> User-Agent: curl/7.52.1
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Date: Wed, 26 Jun 2019 20:39:44 GMT
< Content-Type: text/plain
< X-Your-Address-Is: 193.10.5.2
< Content-Encoding: identity
< Expires: Wed, 26 Jun 2019 21:00:00 GMT
< Vary: X-Or-Diff-From-Consensus
<
{ [1787 bytes data]
100 1941k 0 1941k 0 0 245k 0 --:--:-- 0:00:07 --:--:-- 271k* Curl_http_done: called premature == 0
100 2147k 0 2147k 0 0 252k 0 --:--:-- 0:00:08 --:--:-- 300k
* Closing connection 0
$
More information about the tor-consensus-health
mailing list