Re: [tor-relays] Consensus weight dropped

[Karsten Loesing <karsten@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21/01/15 13:35, Network Operations Center wrote:
> Ah I see, thanks for taking the time investigating this. If there
> is something I need to do to help, please let me know.

You could start a second relay on the same physical machine on a
different port and see whether the bandwidth scanners pick that up.
Give it a day or two, and see if only tor26 and moria1 measure it.

You can find out the latter by fetching the latest votes from all
directory authorities and searching for your nickname and subsequent
"w" lines in them:

https://collector.torproject.org/recent/relay-descriptors/votes/

And of course you'll notice on Atlas whether the consensus weight
fraction of your new relay will be 0.00000% or not.

All the best,
Karsten


> 
> On 21.01.2015 01:22 PM, Karsten Loesing wrote: On 21/01/15 11:54,
> Network Operations Center wrote:
>>>> My dropping consensus overlaps exactly with the blue line on
>>>> that graph time-wise. The 1 Month Graph shows this pretty
>>>> well.
>>>> 
>>>> https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2600
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 
It feels as if I am almost completely dependent on that blue node,
>>>> although since one needs multiple measures, it shouldn't be 
>>>> possible.
> 
> Ah, sorry for being unclear.  The blue line is not bandwidth
> authority number 4, it's the number of relays for which there are
> measurements from 4 bandwidth authorities.
> 
> But here's another graph, specifically for your relay schokomilch:
> 
> https://people.torproject.org/~karsten/volatile/schokomilch-cw-2015-01-21.png
>
> 
> 
> 14C1 is tor26, 4901 is maatuska, and D586 is moria1.  It looks
> like maatuska stopped measuring your relay between December 29 and
> January 5, which is a general problem with maatuska's scanner, not
> specific to your relay, AFAIK.
> 
> And unrelated to this, neither gabelmoo nor longclaw ever measured 
> your relay.  I'd say this is something to investigate and then
> fix.
> 
> All the best, Karsten
>> _______________________________________________ tor-relays
>> mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx 
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> _______________________________________________ tor-relays mailing
> list tor-relays@xxxxxxxxxxxxxxxxxxxx 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJUv5+CAAoJEJd5OEYhk8hIqTwH/0AeNxhZu7zNlkdN3W2F9TT1
k1yAeZrZtf4qfb+rAkTD21njzrFo3VUaO7QhBBZPOuVsLgfWGc9YAVVAINnRQPOq
WzgE7lr/123xbYRZV5if+tcODhrj9WHmnOK7UT+iA3EvekkNU7S4Z1iJh/klxix5
31q36RvDbo/OQIWRV8p+pirwJ5fPes5bDr9B3JbKAHw10XeqG1VlGZVoPaLXR05W
AwQBhU80UsRiZzxH434KwAXY/5iaCY92cLoux+N/B+nAMZ33NGAjCHb530FghpB8
O0KZHawlV+XFMoaEM+il2I1aDoKC+gtmBerdUk93ZD55PxVAjfOBMLrgVWgtbVI=
=j/m5
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays