Just thought I'd throw it out there.
About 5 days ago I setup a new relay - it's consensus weight is still at 20.
Then, I noticed a relay I've been running for about a month all of sudden lost all of it's consensus weight. It was ~17000, now at 20. It's uptime is 25 days, and has downloaded 4.8TB and updated 5.0TB in that time.
Normally, when I have a consensus weight of 20, I also see a measured speed in arm of 160b/s. However, my month old relay's measured speed is showing 136.7Kb/s. This relay was averaging 15-25Mbit/s up until today, but now jumps between 600Kbit - 8Mbit, but mainly between 800Kbit-2Mbit.
My other relays with the same provider have not experienced this, nor have my relays with different providers. Just this one.
The interesting one: https://atlas.torproject.org/#details/D60B02A13F5D9CAFD6EC27A5332C5FEF5B7691...
Matt Speak Freely
Actually I remembered a third relay having problems.
On Friday last week my provider asked me to rate limit one of my relays because it was pumping a lot of data. (Unmetered does have its limits, and I fully appreciate how my provider handled it) I changed the RelayBandwidth from 100Mbit to 50Mbit, and it almost immediately went from averaging 75Mbit/each way to about 7 each way. It's consensus weight dropped like a rock. It's slowly sort of mostly kind of caught up, now in the 25-35/each way range.
(I can sort of understand why it happened - the network was adjusting things to deal with the decreased capacity. But it should not have been such a dramatic drop, then the slow rise. I feel this is little more than nit-picking on my part, though.)
This sort of seems to be in line with the thread: [tor-relays] BWAUTH weightings too volatile. . ."twitchy"
https://atlas.torproject.org/#details/656E73D7D153DE93D5EEAF837D675F8F129A50...
When the consensus weight is retarded, so is my relay.
Just thought I'd add that to the list.
Matt Speak Freely
Zero progress on this, so I thought I'd pop it up again.
I'm only pointing this out because it's interesting, not because I think anyone will do anything about it. It may be interesting to someone looking into the diversity of consensus weights given a small subset from two providers, that is all.
Neither of the two problem relays have gotten rid of their consensus weight of 20. One of my other relays has lost significant consensus, from 11170 to 1720, its now pushing peanuts, or about 1/10 of what it used to.
My oldest relay pushed(in/out) ~10TB last month before losing it's consensus weight. My other relay, brand new, has been up for about a week and still stuck at 20.
All 5 relays come from 2 providers in the euro-region, my other relays are not important so are not displayed.
About ~4 hours ago I restarted the 5 relays to see the fun. Since that time, here is that status of each:
1) Measured speed 165.6Kb/s (arm) Downloaded 50.0GB Uploaded 51.0GB Avg Rate: 66.8Mbit/s (vnstat) Consensus 21200 Provider #1
2) Measured speed 105.4Kb/s (arm) Downloaded 28.7GB Uploaded 29.4GB Consensus 13500 Avg Rate 38.13Mbit/s (vnstat) Provider #2
3) Measured speed 13.4Kb/s (arm) Downloaded 4.1GB Uploaded 4.3GB Consensus 1720 Avg Rate 5.4Mbit/s (vnstat) Provider #2
4) Measured speed 160b/s (arm) Downloaded 3.1GB Uploaded 3.2GB Consensus 20 Avg Rate 3.82Mbit/s (vnstat) Provider #2 **Oldest relay in list
5) Measured speed 160b/s (arm) Downloaded 217MB Uploaded 216MB Consensus 20 Avg Rate 204kbit/s (vnstat) Provider #1 **Newest relay in list
Relay #5 should be acting more like relay #1. Keep in mind though relay #1 was rate limited last week by half because my provider asked me to - it was for a period of time happily doing 75-90Mb/s each way. Relays #2-4 should all be similar, but they're everywhere.
Enjoy.
Matt Speak Freely
I looked at https://atlas.torproject.org/#details/D60B02A13F5D9CAFD6EC27A5332C5FEF5B7691... / 4FreeSpeech for the latest vote:
moria: w Bandwidth=3012 Measured=1890 maatuska: w Bandwidth=3012 Measured=3820 gabelmoo: w Bandwidth=3012 longclaw: w Bandwidth=3012
consensus: w Bandwidth=20 Unmeasured=1
Once you get 3 measurements you should pop over to a real measurement. (How sane it stays is a whole other issue.)
It's possible (although not simplified) to grab historical measurements from archived votes and consensuses and figure out how and when different dirauths voted on you.
-tom
On 12 June 2015 at 12:56, Speak Freely when2plus2is5@riseup.net wrote:
Zero progress on this, so I thought I'd pop it up again.
I'm only pointing this out because it's interesting, not because I think anyone will do anything about it. It may be interesting to someone looking into the diversity of consensus weights given a small subset from two providers, that is all.
Neither of the two problem relays have gotten rid of their consensus weight of 20. One of my other relays has lost significant consensus, from 11170 to 1720, its now pushing peanuts, or about 1/10 of what it used to.
My oldest relay pushed(in/out) ~10TB last month before losing it's consensus weight. My other relay, brand new, has been up for about a week and still stuck at 20.
All 5 relays come from 2 providers in the euro-region, my other relays are not important so are not displayed.
About ~4 hours ago I restarted the 5 relays to see the fun. Since that time, here is that status of each:
Measured speed 165.6Kb/s (arm) Downloaded 50.0GB Uploaded 51.0GB Avg Rate: 66.8Mbit/s (vnstat) Consensus 21200 Provider #1
Measured speed 105.4Kb/s (arm) Downloaded 28.7GB Uploaded 29.4GB Consensus 13500 Avg Rate 38.13Mbit/s (vnstat) Provider #2
Measured speed 13.4Kb/s (arm) Downloaded 4.1GB Uploaded 4.3GB Consensus 1720 Avg Rate 5.4Mbit/s (vnstat) Provider #2
Measured speed 160b/s (arm) Downloaded 3.1GB Uploaded 3.2GB Consensus 20 Avg Rate 3.82Mbit/s (vnstat) Provider #2 **Oldest relay in list
Measured speed 160b/s (arm) Downloaded 217MB Uploaded 216MB Consensus 20 Avg Rate 204kbit/s (vnstat) Provider #1 **Newest relay in list
Relay #5 should be acting more like relay #1. Keep in mind though relay #1 was rate limited last week by half because my provider asked me to - it was for a period of time happily doing 75-90Mb/s each way. Relays #2-4 should all be similar, but they're everywhere.
Enjoy.
Matt Speak Freely _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
It has hit me again aswell, consensus dropped from 40,000+ to 20 after serving 100+ mbit daily to the Tor network:
06/12/2015 621.04 GiB | 692.11 GiB | 1.28 TiB | 127.49 Mbit/s 06/13/2015 565.29 GiB | 629.45 GiB | 1.17 TiB | 116.00 Mbit/s 06/14/2015 649.90 GiB | 698.06 GiB | 1.32 TiB | 130.87 Mbit/s 06/15/2015 522.81 GiB | 571.44 GiB | 1.07 TiB | 106.24 Mbit/s 06/16/2015 42.94 GiB | 90.53 GiB | 133.48 GiB | 12.96 Mbit/s 06/17/2015 48.09 GiB | 90.90 GiB | 138.99 GiB | 13.49 Mbit/s
:<
On 09.06.2015 06:43 PM, Speak Freely wrote:
Just thought I'd throw it out there.
About 5 days ago I setup a new relay - it's consensus weight is still at 20.
Then, I noticed a relay I've been running for about a month all of sudden lost all of it's consensus weight. It was ~17000, now at 20. It's uptime is 25 days, and has downloaded 4.8TB and updated 5.0TB in that time.
Normally, when I have a consensus weight of 20, I also see a measured speed in arm of 160b/s. However, my month old relay's measured speed is showing 136.7Kb/s. This relay was averaging 15-25Mbit/s up until today, but now jumps between 600Kbit - 8Mbit, but mainly between 800Kbit-2Mbit.
My other relays with the same provider have not experienced this, nor have my relays with different providers. Just this one.
The interesting one: https://atlas.torproject.org/#details/D60B02A13F5D9CAFD6EC27A5332C5FEF5B7691...
Matt Speak Freely _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Yeah, I've given up. I won't be renewing most of my relays this month. :(
Matt Speak Freely
On 2015-06-19 17:59, Speak Freely wrote:
Yeah, I've given up. I won't be renewing most of my relays this month. :(
Matt Speak Freely
Hi Matt, Sorry that you have had so much trouble with your relays being underutilized. I am now working to fix/refactor Tor's Bandwidth Authority system as a full-time project, now recently (this month) funded by OTF (https://opentechfund.org). You can follow the state of the project at:
https://trac.torproject.org/projects/tor/ticket/13630
Admittedly it's been a while since I started looking into this issue - one of the things we'd hoped was that the BwAuth system could be replaced by PeerFlow, but unfortunately it is still an open research problem, and so the BwAuths are here to stay for now. My first priority is to attack the unmeasured relays problem.
Hopefully this gives you some confidence that these issues will be addressed. I hope that if you do decide to suspend your relays you will bring them back in the future. You can also find me on IRC as aagbsn.
--Aaron
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
Aaron Gibson -
Network Operations Center -
Speak Freely -
Tom Ritter