Hello,
I noticed on my Tor relay that deploying 0.2.6.3 resulted in the bandwidth going up an down a lot which can be seen here:
https://globe.torproject.org/#/relay/CE75BF0972ADD52AF8807602374E495C815DB30...
It looks like I am not the only one. This CCC hosted relay (different OS, provider, etc.) appears to have the same thing happening:
https://globe.torproject.org/#/relay/9BDF3EEA1D33AA58A2EEA9E6CA58FB8A667288F...
It is hard to filter relays per version right now (maybe something onionoo could support?). Are others experiencing the same problems?
On Fri, Feb 20, 2015 at 9:50 AM, Christian Sturm reezer@reezer.org wrote:
Hello,
I noticed on my Tor relay that deploying 0.2.6.3 resulted in the bandwidth going up an down a lot which can be seen here:
https://globe.torproject.org/#/relay/CE75BF0972ADD52AF8807602374E495C815DB30...
It looks like I am not the only one. This CCC hosted relay (different OS, provider, etc.) appears to have the same thing happening:
https://globe.torproject.org/#/relay/9BDF3EEA1D33AA58A2EEA9E6CA58FB8A667288F...
It is hard to filter relays per version right now (maybe something onionoo could support?). Are others experiencing the same problems?
Roger thinks it could be related to this change:
o Minor bugfixes (statistics): - Increase period over which bandwidth observations are aggregated from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
If that's so, the likeliest explanation is that Globe is not displaying the bandwidths correctly with the new intervals. Trying to get it investigated...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 20/02/15 15:50, Christian Sturm wrote:
I noticed on my Tor relay that deploying 0.2.6.3 resulted in the bandwidth going up an down a lot which can be seen here:
https://globe.torproject.org/#/relay/CE75BF0972ADD52AF8807602374E495C815DB30...
It looks like I am not the only one. This CCC hosted relay (different OS, provider, etc.) appears to have the same thing happening:
https://globe.torproject.org/#/relay/9BDF3EEA1D33AA58A2EEA9E6CA58FB8A667288F...
Ah,
that looks like an issue in Onionoo, not in little-t-tor. I think this is caused by this recent change:
https://trac.torproject.org/projects/tor/ticket/13988
I'll have to fix Onionoo. Could take a few days though.
It is hard to filter relays per version right now (maybe something onionoo could support?). Are others experiencing the same problems?
There's already a ticket for this:
https://trac.torproject.org/projects/tor/ticket/14879
All the best, Karsten
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 20/02/15 16:10, Karsten Loesing wrote:
On 20/02/15 15:50, Christian Sturm wrote:
I noticed on my Tor relay that deploying 0.2.6.3 resulted in the bandwidth going up an down a lot which can be seen here:
https://globe.torproject.org/#/relay/CE75BF0972ADD52AF8807602374E495C815DB30...
It looks like I am not the only one. This CCC hosted relay (different OS, provider, etc.) appears to have the same thing happening:
https://globe.torproject.org/#/relay/9BDF3EEA1D33AA58A2EEA9E6CA58FB8A667288F...
Ah,
that looks like an issue in Onionoo, not in little-t-tor. I think this is caused by this recent change:
https://trac.torproject.org/projects/tor/ticket/13988
I'll have to fix Onionoo. Could take a few days though.
There, somebody filed a ticket, and I posted a branch for review:
https://trac.torproject.org/projects/tor/ticket/14984
For future updates, please see the ticket.
All the best, Karsten
tor-relays@lists.torproject.org
-
Christian Sturm -
Karsten Loesing -
Nick Mathewson