Opened 7 years ago

Closed 7 years ago

#7587 closed defect (fixed)

atlas not creating all graphs for a certain node

Reported by: kargig Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/Onionoo Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

traffic graphs generation for node with id 0b37323298ff98cd86ed404895bb27b7426e8ae1 seem to have some problems since August. The node is constantly up and running for many months and the graphs about advertised bw and exit/guard probability seem to work fine for that period.

https://atlas.torproject.org/#details/0b37323298ff98cd86ed404895bb27b7426e8ae1

could it have something to do with the local node configuration ?

Child Tickets

Attachments (1)

0B37323298FF98CD86ED404895BB27B7426E8AE1 (37.5 KB) - added by karsten 7 years ago.
Onionoo bandwidth status file

Download all attachments as: .zip

Change History (6)

comment:1 Changed 7 years ago by karsten

Owner: changed from hellais to karsten
Status: newassigned

I'll have a look at the original descriptors to see what's going on there.

Do you have any other data that confirms that this relay was constantly up and running since August? For example, do you have traffic stats from your provider?

What local node configuration do you think might have something to do with this?

comment:2 Changed 7 years ago by kargig

I'm running this node and I'm pretty sure it constantly has traffic as do graphs from torstatus.blutmagie show.

I have no idea what local setting could be the problem, I was just guessing.
fwiw this node also has an IPv6 enabled ORport, if that matters at all...

Changed 7 years ago by karsten

Onionoo bandwidth status file

comment:3 Changed 7 years ago by karsten

Component: AtlasOnionoo

Replying to kargig:

I'm running this node and I'm pretty sure it constantly has traffic as do graphs from torstatus.blutmagie show.

Okay.

I have no idea what local setting could be the problem, I was just guessing.
fwiw this node also has an IPv6 enabled ORport, if that matters at all...

The IPv6 OR port shouldn't matter here.

I just attached the bandwidth status file that Onionoo (the data provider behind Atlas) produces from parsing your relay's descriptors. There are for sure some gaps in there. I suspect there's some weird parsing problem, or something. I couldn't find the bug so far, and I'm left without Internet for a day or two. I'll look closer after that.

Changing to Onionoo, because this is not just a display problem in Atlas.

comment:4 Changed 7 years ago by karsten

Found the problem. Your relay descriptor has a transport line that the version of the descriptor-parsing library that Onionoo uses does not understand. The fix is to upgrade to the most recent library version and to re-process all past descriptors with such a line. The latter will take some time. I'll fix this in a few days from now.

Thanks for the bug report!

comment:5 Changed 7 years ago by karsten

Resolution: fixed
Status: assignedclosed

Fixed. The bandwidth graphs now look normal again. Closing.

Note: See TracTickets for help on using tickets.