Hi,
I was wondering why onionoo reported empty platform strings for a growing number of relays.
I wanted to confirm that by looking at collector data, but then I noticed that there is a problem with collector data itself.
Files in [1] usually have a size of around 1 MB, currently they are at 1KB (basically empty).
@thomas: Is that the cause for your onionoo instance issue?
[1] https://collector.torproject.org/recent/relay-descriptors/server-descriptors...
In the event of collector missing data, there are (at least) two backup instances. One is at bwauth.ritter.vg - no website, just files.
Does that have the same issue?
-tom
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
In the event of collector missing data, there are (at least) two backup instances. One is at bwauth.ritter.vg - no website, just files.
Does that have the same issue?
https://bwauth.ritter.vg/rsync/relay-descriptors/server-descriptors-cat/
looks fine.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/08/15 16:16, nusenu wrote:
In the event of collector missing data, there are (at least) two backup instances. One is at bwauth.ritter.vg - no website, just files.
Does that have the same issue?
https://bwauth.ritter.vg/rsync/relay-descriptors/server-descriptors-cat/
looks fine.
Oh, crap. That's my fault. I deployed a CollecTor patch yesterday that's acting up. I know what the problem is, I now need to fix it and clean up the mess. Ewww.
Here's the (still broken) patch, if you care:
https://gitweb.torproject.org/karsten/metrics-db.git/commit/?h=no-cat&id...
(If you really care, the problem is that I forgot to update the boolean[] arrays.)
Good catch, Nusenu!
All the best, Karsten