[tor-bugs] Re: #1206 [Tor - Relay]: Fluxe3 is not a guard

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#1206: Fluxe3 is not a guard
--------------------------------+-------------------------------------------
 Reporter:  Sebastian           |         Type:  defect     
   Status:  new                 |     Priority:  minor      
Milestone:  Tor: 0.2.2.x-final  |    Component:  Tor - Relay
  Version:  0.2.2.6-alpha       |   Resolution:  None       
 Keywords:                      |       Parent:             
--------------------------------+-------------------------------------------

Old description:

> Fluxe3 isn't considered a guard (only one of the authorities votes for
> it).
> It has been up for 13 days, before that it had a downtime for ~30
> minutes,
> and before that it was running for a week. Before that it was offline.
>
> There are a few things that seem to be strange. When arma looked at
> what moria thinks about fluxe3 three days ago, moria thought that
> fluxe3's
> uptime was 18 days. It somehow missed the fact that the descriptor
> changed
> to reflect the new uptime.
>
> The other question is, does this influence why Fluxe3 is not a guard? Or
> are
> there other issues?
>
> [Automatically added by flyspray2trac: Operating System: All]

New description:

 Fluxe3 isn't considered a guard (only one of the authorities votes for
 it).
 It has been up for 13 days, before that it had a downtime for ~30 minutes,
 and before that it was running for a week. Before that it was offline.

 There are a few things that seem to be strange. When arma looked at
 what moria thinks about fluxe3 three days ago, moria thought that fluxe3's
 uptime was 18 days. It somehow missed the fact that the descriptor changed
 to reflect the new uptime.

 The other question is, does this influence why Fluxe3 is not a guard? Or
 are
 there other issues?

 [Automatically added by flyspray2trac: Operating System: All]

--

Comment(by mikeperry):

 Actually, I'm now less convinced that the WFU calculation was done wrong
 in this case.

 Based on the WFU numbers, prior to the 20 uptime, the router should have
 been up for something like 9759/(0.95^40) or 81325s (22 hours) in the last
 149363/(0.95^20) 244691s (14 days).

 Sebastian, in your original report you said that before the 20 days of
 uptime, Fluxe3 was "offline". Might it have been offline for about 2
 weeks, maybe with a day of uptime somewhere in there? If so, WFU might be
 correct, and we just need to think about setting better thresholds.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1206#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online