#28691 closed defect (worksforme)

dirauth longclaw network connectivity impaired

Reported by: starlight Owned by:
Priority: Medium Milestone:
Component: Core Tor/DirAuth Version:
Severity: Normal Keywords:
Cc: micah, juga Actual Points:
Parent ID: #28639 Points:
Reviewer: Sponsor:


For quite some time the longclaw dirauth has apparently been operating with badly degraded network connectivity resulting in degraded consensus votes. Per


           Only in vote      In vote and consensus   Only in consensus
           ===============   =====================   =================
longclaw                     10 Authority
                             3 BadExit
           1 Exit            857 Exit
           5 Fast            754 Fast                !4857 Fast
           21 Guard          453 Guard               !2028 Guard
           4 HSDir           476 HSDir               !2952 HSDir
                             6472 Running            !13 Running
           52 Stable         5412 Stable             !26 Stable
           1 V2Dir           6443 V2Dir
                             7439 Valid
                             117 FallbackDir
                             67 Unmeasured
           38 DescMismtch    0 DescMismtch

Of particular note longclaw marks close to 5000 relays as "not fast" compare to the consensus where other authorities see no more than about 100 as not fast w/r/t the overall consensus. A close correlation exists between "not fast" relays in longclaw's consensus and relays omitted by the SBWS scanner associated with this authority. Longclaw dirauth is not voting 2000 guard relay as such.

Child Tickets

Change History (3)

comment:1 Changed 22 months ago by teor

Cc: micah juga added

This could be a sbws bug.

comment:2 Changed 22 months ago by teor

Parent ID: #28639

This is probably #28639 or #28663.

comment:3 Changed 19 months ago by juga

Resolution: worksforme
Status: newclosed

This was probably because of #28355 (#29710).
Maybe the running instance was was not the version that fixed #28442.
We can reopen if this happen again.

Note: See TracTickets for help on using tickets.