Re: [tor-relays] More consensus weight problems
Rah rah rah... Emailed Aaron directly by accident. Here's the email: Hello, First of all, I love Tor. I love Tor Browser, and I love running relays. When the problems are solved, I will most likely spin up more relays. I'm leaving my fastest relay running, as a method of checking the status for myself. The rest have already started to expire, and within the next week or so most of the other ones will have expired as well. I'm going to try tor-dev-alpha 2.7.1 and change fingerprints, as per a suggestion from s7r, seeing as how I have nothing to lose. I just wish the bwauths could scan relays based off previous relative consensus weights... If this particular relay was at 27000, it should be higher on the list to check compared to another one I have that is at 487. My one relay was blazing fast with thousands of connections, my other is painfully useless with dozens, but my fastest one lost its consensus while the slowest one kept it's consensus. It just seems silly. That being said, I don't know how/if the bwauths scan in any order or just willy-nilly, (that's not entirely true, I know it's segmented to some degree as I recall reading a blog post about how it's chopped up) but... I'd be much less upset if my best relays worked and my worst relays didn't. More complaining... bleh. One thing I would like to point out though... it appears... These problems have at least a casual relationship with MyFamily. One group of MyFamily is completely done - all of them stuck at 20. Another group of MyFamily is working happily. I've been doing some tests over the past few months trying to understand why I keep having problems, and one thing has consistently popped up... MyFamily. As one of MyFamily lost consensus, another family gained consensus back on or around the same time. Yes, especially nusenu, I know I'm supposed to have it all configured to be under 1 MyFamily... But in a way I'm glad I didn't, as the casual relationship I see really could only be seen having done what I did. I say casual because I have no proof of causation. But... it is interesting. If no one else has experienced similar problems, then I'd chock it up to a completely unexpected unrelated set of mysterious circumstances that should not have happened for which there is no explanation. Aaron, if there is anything I can do to help you please let me know. So in conclusion, I'm not done, I'm just not happy. This was supposed to be a short email, oops. Matt Speak Freely
I did as s7r suggested, updated to 0.2.7.1-alpha-dev, and changed fingerprints. And we're still crippled by CW of 20. (Yes, yes, I know. The relay has gone back to stage 1/3 because the fingerprints changed.) Uptime: > 48 hours Upload/download : 2.1GB, works out to a blazingly fast speed of 12.1KB/s ------------------------------------- ------------------------------------- I just now did a 1GB speed test while running the relay. (wget -O /dev/null http://speedtest.wdc01.softlayer.com/downloads/test1000.zip) Length: 1073741824 (1.0G) [application/zip] Saving to: `/dev/null' 100%[====================================>] 1,073,741,824 14.1M/s in 86s 2015-07-02 09:23:31 (11.9 MB/s) - `/dev/null' saved [1073741824/1073741824] ------------------------------------- ------------------------------------- Don't forget to smile! Matt Speak Freely
Takes a full two weeks for the new-relay cap to be aged-out. Patience. At 13:33 7/2/2015 +0000, Speak Freely wrote:
I did as s7r suggested, updated to 0.2.7.1-alpha-dev, and changed fingerprints.
And we're still crippled by CW of 20. (Yes, yes, I know. The relay has gone back to stage 1/3 because the fingerprints changed.)
Starlight, I created this relay on Friday, shortly after you told me to be patient. https://atlas.torproject.org/#details/41C526E3C1441A3CDE9B605002643B94F3750E... Uptime: 3 days 23 hours CW: 1100 (yesterday it was at 740) It gained consensus after 48 hours, but you said it would take 2 weeks? How is this possible? Matt Speak Freely
Hi Matt, Which relays are you have issues with? Kind Regards, Joshua Lee Tucker @tuckerwales http://tucker.wales
On 6 Jul 2015, at 19:41, Speak Freely <when2plus2is5@riseup.net> wrote:
Starlight,
I created this relay on Friday, shortly after you told me to be patient.
https://atlas.torproject.org/#details/41C526E3C1441A3CDE9B605002643B94F3750E... Uptime: 3 days 23 hours CW: 1100 (yesterday it was at 740)
It gained consensus after 48 hours, but you said it would take 2 weeks? How is this possible?
Matt Speak Freely
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hey Josh, (The following is the only sentence that matters in this email) I was just curious about the statement that it "takes a full 2 weeks for the new-relay cap to be aged-out". (The following is only background information in case you were curious, because it's been a hell of a long standing issue.) Oh, damn near all of them. If I recall correctly, it all started in March, and just got worse and worse, and by the time May rolled around I was just wasting money. However, I let about 5 exits slide on their renewal this month as all but 2 non-exit relays lost consensus completely, perpetually locked at 20. At one point, I was merrily pumping well over 200Mbit upload and download, over 400Mbit/s total over all the relays. Then one day, literally 1 day, I was not so merrily pumping ~100k/s total over all relays. A few months have now lapsed, and I've mostly given up. I now just try things and report in the hopes that it will jog someones memory or give some insight into what's going on. Doing everything I could, limited though it may be, to keep my fastest relay running, which at one point was doing 125Mbit each way, over a period of over a month I tried resetting the keys, updating the software, resetting the keys again, then finally upgrading to the 0.2.7.x alpha, resetting the keys again, and still nothing. Consensus weight = 20 == nothing. Then I got upset and complained, and starlight said I had to wait 2 weeks for the new-relay cap to be released, which I knew to be untrue as I had never experienced that before, because I have fond memories of times long ago when my relays worked. So for fun, I re-spun one of my working relays. Fresh install, new onion keys. It gained consensus after ~48 hours, instead of the 336 hours (2wks) starlight indicated. Matt Speak Freely
I just want to chime in with my own consensus weight problem. FF1678164E0FFF1DACA45E3DCDE16E49FF1374BE has been running for over 70 days and still has a consensus of 20, I don't think it has ever changed since it was started. Looking at the consensus it is unmeasured=1 by every authority. Any ideas? -- Carlin
On 7 July 2015 at 09:04, Carlin Bingham <cb@viennan.net> wrote:
I just want to chime in with my own consensus weight problem.
FF1678164E0FFF1DACA45E3DCDE16E49FF1374BE has been running for over 70 days and still has a consensus of 20, I don't think it has ever changed since it was started.
Looking at the consensus it is unmeasured=1 by every authority.
Any ideas?
It's actually only unmeasured by two: http://131.188.40.189/tor/status-vote/current/authority (gabelmoo) http://199.254.238.52/tor/status-vote/current/authority (longclaw) The other two have measured it: http://171.25.193.9:443/tor/status-vote/current/authority (maatuska, 330) http://128.31.0.34:9131/tor/status-vote/current/authority (moria, 325) -tom
participants (5)
-
Carlin Bingham -
josh＠tucker.wales -
Speak Freely -
starlight.2015q2＠binnacle.cx -
Tom Ritter