Opened 3 years ago

Last modified 9 months ago

#15799 assigned defect

Find out why different instances may report different timestamps in last_changed_address_or_port

Reported by: cypherpunks Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Onionoo Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Karsten asked me to open a ticket for this, so I do.

diff between onionoo.tpo vs. onionoo.thecthulhu.com

< 259D44BDF3734077902CD71606BAD95F994A606B"2015-04-13 08:00:00
---
> 259D44BDF3734077902CD71606BAD95F994A606B"2015-04-11 12:00:00


< 3737F4542BBA0C43345BCD91C4F1E194418B313F"2015-02-14 12:00:00
---
> 3737F4542BBA0C43345BCD91C4F1E194418B313F"2015-02-15 12:00:00


< 9F938AE96C6B63F726BB885E4F2D1319C84A25BB"2015-04-12 14:00:00
---
> 9F938AE96C6B63F726BB885E4F2D1319C84A25BB"2015-04-11 12:00:00


< 4E8CE6F5651E7342C1E7E5ED031E82078134FB0D"2015-01-28 11:00:00
---
> 4E8CE6F5651E7342C1E7E5ED031E82078134FB0D"2015-01-26 03:00:00


< 73AB1555F0DA2E6D6B2AB2A603A8CB34F2981B3D"2014-12-30 20:00:00
---
> 73AB1555F0DA2E6D6B2AB2A603A8CB34F2981B3D"2014-12-30 13:00:00

Child Tickets

Change History (7)

comment:1 Changed 3 years ago by cypherpunks

relay EA7642C6940BF6571267F068EF289B93BE82F169 (from 2015-04-25 08:00:00):

tpo:
2015-01-04 04:00:00

tct:
2015-01-26 03:00:00

comment:2 Changed 3 years ago by karsten

I looked up one case in the descriptor archives, and in that case torproject.org is right and thecthulhu.com is wrong:

< 9F938AE96C6B63F726BB885E4F2D1319C84A25BB"2015-04-12 14:00:00   <- torproject.org
---
> 9F938AE96C6B63F726BB885E4F2D1319C84A25BB"2015-04-11 12:00:00   <- thecthulhu.com

But I'm not sure why thecthulhu.com gives out that timestamp, because nothing changed at that time. And I'm not sure how to investigate. Hmm.

comment:3 Changed 10 months ago by karsten

Severity: Normal
Summary: differences in details document: different views of last_changed_address_or_portFind out why different instances may report different timestamps in last_changed_address_or_port

Tweak summary.

comment:4 Changed 10 months ago by karsten

Keywords: metrics-2018 added

comment:5 Changed 10 months ago by karsten

Keywords: metrics-2017 added; metrics-2018 removed

comment:6 Changed 10 months ago by karsten

Owner: set to metrics-team
Status: newassigned

comment:7 Changed 9 months ago by karsten

Keywords: metrics-2017 removed

I just looked into possible differences between omeiense and oo-hetzner-03 and found a couple entries from 2017-08-08. Here are the first five:

< {"fingerprint":"00D86ED7B4F6E5CCEEBDE01A5BE0C757B879000E","last_changed_address_or_port":"2017-08-08 17:00:00"},
---
> {"fingerprint":"00D86ED7B4F6E5CCEEBDE01A5BE0C757B879000E","last_changed_address_or_port":"2017-08-08 18:00:00"},


< {"fingerprint":"06F02BE6C9A817A1C9A3402DE0009CBE0EE92D61","last_changed_address_or_port":"2017-08-08 13:00:00"},
---
> {"fingerprint":"06F02BE6C9A817A1C9A3402DE0009CBE0EE92D61","last_changed_address_or_port":"2017-08-08 18:00:00"},


< {"fingerprint":"071AA2B049C14412A839C0366D3FED260A782BA7","last_changed_address_or_port":"2017-08-08 16:00:00"},
---
> {"fingerprint":"071AA2B049C14412A839C0366D3FED260A782BA7","last_changed_address_or_port":"2017-08-08 18:00:00"},


< {"fingerprint":"0CD5EBCD07CE9422CF6FC59793683D6002A83C61","last_changed_address_or_port":"2017-08-08 11:00:00"},
---
> {"fingerprint":"0CD5EBCD07CE9422CF6FC59793683D6002A83C61","last_changed_address_or_port":"2017-08-08 18:00:00"},


< {"fingerprint":"0F3AB504907E10FE6CC48A23E8126936EC28A337","last_changed_address_or_port":"2017-08-08 17:00:00"},
---
> {"fingerprint":"0F3AB504907E10FE6CC48A23E8126936EC28A337","last_changed_address_or_port":"2017-08-08 18:00:00"},

After some digging I found that that was the date when oo-hetzner-03 switched from using its own short history to using omeiense's year old history.

This is the only case of differences between omeiense and oo-hetzner-03 in the last three months. All subsequent entries are exactly the same.

I'd say let's accept that there can be minor differences in such edge cases like setting up a new service instance and move on.

I'm removing the metrics-2017 keyword and leaving this ticket open, just in case somebody else wants to investigate further. But I wouldn't mind us closing it, either.

Note: See TracTickets for help on using tickets.