Dear list,
My Exit:
https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99...
My Consendus Weight dropped to 20 today 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.
Any ideas what to do or just sit it out ?
On 2017-06-27 12:35:21, "Sebastian Urbach" sebastian@urbach.org wrote:
Dear list,
My Exit:
https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99...
My Consendus Weight dropped to 20 today 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.
Any ideas what to do or just sit it out ? -- Sincerely yours / M.f.G. / Sincères salutations
Sebastian Urbach
Same for my non-exit: https://atlas.torproject.org/#details/855BC2DABE24C861CD887DB9B2E950424B49FC...
Looks like the drop in cw coincided with messages like these in the log: Jun 27 04:35:48.000 [warn] Received http status code 502 ("Bad Gateway") from server '154.35.175.225:80' while fetching "/tor/server/d/44C3629D79C5366209DB976F1F1588A39B923123+C4716B2DA2AB2CAC2DA0256CD2484050B75371BF.z". I'll try again soon. <snip>
154.35.175.225 is the authority server faravahar which have had network issues in the past.
Hello,
Same for my exit. I just count that 220 exit relays over 869 have their Consensus Weight at 20. Best,
Florentin
On 2017-06-27 12:49, Logforme wrote:
On 2017-06-27 12:35:21, "Sebastian Urbach" sebastian@urbach.org wrote:
Dear list,
My Exit:
https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99...
My Consendus Weight dropped to 20 today 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.
Any ideas what to do or just sit it out ? -- Sincerely yours / M.f.G. / Sincères salutations
Sebastian Urbach
Same for my non-exit: https://atlas.torproject.org/#details/855BC2DABE24C861CD887DB9B2E950424B49FC...
Looks like the drop in cw coincided with messages like these in the log: Jun 27 04:35:48.000 [warn] Received http status code 502 ("Bad Gateway") from server '154.35.175.225:80' while fetching "/tor/server/d/44C3629D79C5366209DB976F1F1588A39B923123+C4716B2DA2AB2CAC2DA0256CD2484050B75371BF.z". I'll try again soon.
<snip>
154.35.175.225 is the authority server faravahar which have had network issues in the past.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
TL;DR:
Faravahar is down, that's probably what's causing it.
On 27 Jun 2017, at 21:05, Florentin Rochet florentin.rochet@uclouvain.be 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@urbach.org wrote:
... My Exit:
https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99...
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/CF6D0AAFB385BE71B8E111FC5CFF4B47923733...
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 ------------------------------------------------------------------------
Dear list,
Well Faravahar is finally back but im still wondering why my System (located in France) is measured by exactly 1 System a few thousand miles away.
-- Sincerely yours / M.f.G. / Sincères salutations
Sebastian Urbach
--------------------------------------------------------------------------- Those who surrender freedom for security will not have, nor do they deserve, either one. --------------------------------------------------------------------------- Benjamin Franklin (1706-1790)
Am 27. Juni 2017 14:04:50 schrieb teor teor2345@gmail.com:
TL;DR:
Faravahar is down, that's probably what's causing it.
On 27 Jun 2017, at 21:05, Florentin Rochet florentin.rochet@uclouvain.be 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@urbach.org wrote:
... My Exit:
https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99...
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/CF6D0AAFB385BE71B8E111FC5CFF4B47923733...
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@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Tue, Jun 27, 2017 at 03:52:31PM +0200, Sebastian Urbach wrote:
Well Faravahar is finally back but im still wondering why my System (located in France) is measured by exactly 1 System a few thousand miles away.
Actually, it's measured by three bwauths. You can look it up on https://www.freehaven.net/~arma/moria1-v3-status-votes (Careful, it is a very large file.)
In ParEpistemenTaksis's case, it has bwauth measurements from moria1, longclaw, and Faravahar.
It looks like teor's thought that at least one bwauth is sufficient to get moved off of consensus weight 20 wasn't right. You need three: https://gitweb.torproject.org/tor.git/tree/src/or/dirvote.c?id=tor-0.3.0.8#n...
Which on further thought makes sense -- if only rogue dir auth could by itself declare that all its friends in the unmeasured relays set are actually consensus weight 1e9, that wouldn't be cool.
So then your question would be "ok, there are four bwauths, how come gabelmoo hasn't measured me?" https://consensus-health.torproject.org/#bwauthstatus And that is a fine question, but I fear the answer is the same as all the other "why is the torflow stuff broken" questions. Tom Ritter has been looking lately at making it better, at least.
(Thanks for running an exit relay! :)
--Roger
tor-relays@lists.torproject.org
-
Florentin Rochet -
Logforme -
Roger Dingledine -
Sebastian Urbach -
teor