TL;DR:
Faravahar is down, that's probably what's causing it.
On 27 Jun 2017, at 21:05, Florentin Rochet <florentin.rochet@xxxxxxxxxxxx>
wrote:
...
Same for my exit. I just count that 220 exit relays over 869 have their
Consensus Weight at 20.
...
On 2017-06-27 12:49, Logforme wrote:
On 2017-06-27 12:35:21, "Sebastian Urbach" <sebastian@xxxxxxxxxx> wrote:
...
My Exit:
https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99FE
My Consendus Weight dropped to 20 today
Hi Florentin, Sebastian,
Faravahar is down, so we are down to 3 bandwidth authorities, which
changes the median bandwidth for some relays. It also means that
relays that were only measured by Faravahar will get a bandwidth of
20. (Relays with 1 or 2 measurements will have unstable bandwidths.)
You can just wait it out until North America wakes up :-)
You can check the measurement details for your relay if you want.
There's a wiki page for relay operators with slow relays:
https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow
and i found the following in notices.log:
Jun 27 12:03:35.000 [warn] http status 502 ("Bad Gateway") reason
unexpected while uploading descriptor to server '154.35.175.225:80').
Jun 27 12:07:35.000 [warn] Received http status code 502 ("Bad Gateway")
from server '154.35.175.225:80' while fetching
"/tor/server/d/C8B7BA97808F42802FCC2DF231A85ACB5B8D848A.z". I'll try again
soon.
…
Faravahar is down, so that might be why its caching proxy is giving
this response.
https://atlas.torproject.org/#details/CF6D0AAFB385BE71B8E111FC5CFF4B47923733BC
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
------------------------------------------------------------------------
----------
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays