Opened 7 years ago

Closed 7 years ago

#4878 closed defect (implemented)

Indicate severities of consensus-health messages

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

Description

2012-01-07 18:03:08 <nsa> \^Bor\^B: [consensus-health] The consensuses downloaded from the following authorities are missing signatures from previously voting authorities: dizum, gabelmoo, maatuska, moria1, tor26, urras
2012-01-07 18:03:08 <nsa> \^Bor\^B: [consensus-health] The following directory authorities are not reporting bandwidth scanner results: ides
2012-01-07 18:03:09 <nsa> \^Bor\^B: [consensus-health] The following directory authorities did not return a consensus within a timeout of 60 seconds: dannenberg, ides

2012-01-08 00:11:05 <nsa> \^Bor\^B: [consensus-health] The consensuses downloaded from the following authorities are missing signatures from previously voting authorities: dizum, gabelmoo, moria1, urras
2012-01-08 00:11:05 <nsa> \^Bor\^B: [consensus-health] The consensuses published by the following directory authorities are more than 1 hour old and therefore not fresh anymore: dizum, gabelmoo, moria1, urras
2012-01-08 00:11:07 <nsa> \^Bor\^B: [consensus-health] The following directory authorities did not return a consensus within a timeout of 60 seconds: dannenberg, ides, maatuska, tor26

2012-01-08 18:03:10 <nsa> \^Bor\^B: [consensus-health] The consensuses downloaded from the following authorities are missing signatures from previously voting authorities: dizum, gabelmoo, moria1, tor26, urras
2012-01-08 18:03:10 <nsa> \^Bor\^B: [consensus-health] The following directory authorities did not return a consensus within a timeout of 60 seconds: dannenberg, ides, maatuska
2012-01-08 18:03:11 <nsa> \^Bor\^B: [consensus-health] The following directory authorities set conflicting or invalid consensus parameters: gabelmoo CircuitPriorityHalflifeMsec=30000 circwindow=1000 refuseunknownexits=1, moria1 CircuitPriorityHalflifeMsec=30000 cbtnummodes=3 cbtquantile=80 circwindow=1000 refuseunknownexits=1
2012-01-08 18:03:13 <nsa> \^Bor\^B: [consensus-health] We're missing votes from the following directory authorities: dannenberg, ides

Quick! Which of these sets of messages tells us that the network is about to go down in flames?

Child Tickets

Change History (6)

comment:1 Changed 7 years ago by karsten

Sure, we can add severities to warning messages. Can you suggest some severities for the following messages? Note that we can assign different severities depending on the number of authorities listed after colons:

  • "The following directory authorities did not return a consensus within a timeout of 60 seconds:"
  • "The following directory authorities did not return a consensus within a timeout of 60 seconds:"
  • "The consensuses published by the following directory authorities are more than 1 hour old and therefore not fresh anymore:"
  • "The following directory authorities do not support the consensus method that the consensus uses:"
  • "The following directory authorities recommend other client versions than the consensus:"
  • "The following directory authorities recommend other server versions than the consensus:"
  • "The following directory authorities set conflicting or invalid consensus parameters:"
  • "The certificates of the following directory authorities expire within the next three months:"
  • "The certificates of the following directory authorities expire within the next two months:"
  • "The certificates of the following directory authorities expire within the next 14 days:"
  • "We're missing votes from the following directory authorities:"
  • "The following directory authorities are not reporting bandwidth scanner results:"
  • "The consensuses downloaded from the following authorities are missing votes that are contained in consensuses downloaded from other authorities:"
  • "The consensuses downloaded from the following authorities are missing signatures from previously voting authorities:"

comment:2 in reply to:  1 ; Changed 7 years ago by rransom

Replying to karsten:

Sure, we can add severities to warning messages. Can you suggest some severities for the following messages? Note that we can assign different severities depending on the number of authorities listed after colons:

  • "The following directory authorities did not return a consensus within a timeout of 60 seconds:"
  • "The following directory authorities did not return a consensus within a timeout of 60 seconds:"
  • "The consensuses published by the following directory authorities are more than 1 hour old and therefore not fresh anymore:"

WARNING if the total number of dirauths which did not respond or did not return a fresh consensus is less than (n_dirauths_total - n_dirauths_needed_to_sign_consensus); ERROR otherwise.

Add a new message separate from the above (severity ERROR) if no authority returned a fresh consensus.

  • "The following directory authorities do not support the consensus method that the consensus uses:"

WARNING

  • "The following directory authorities recommend other client versions than the consensus:"
  • "The following directory authorities recommend other server versions than the consensus:"

NOTICE

  • "The following directory authorities set conflicting or invalid consensus parameters:"
  • "The certificates of the following directory authorities expire within the next three months:"
  • "The certificates of the following directory authorities expire within the next two months:"

NOTICE

  • "The certificates of the following directory authorities expire within the next 14 days:"

WARNING

  • "We're missing votes from the following directory authorities:"

WARNING

  • "The following directory authorities are not reporting bandwidth scanner results:"

NOTICE

  • "The consensuses downloaded from the following authorities are missing votes that are contained in consensuses downloaded from other authorities:"
  • "The consensuses downloaded from the following authorities are missing signatures from previously voting authorities:"

WARNING

comment:3 in reply to:  2 Changed 7 years ago by rransom

Replying to rransom:

Replying to karsten:

  • "The certificates of the following directory authorities expire within the next 14 days:"

WARNING

And perhaps we should have an WARNING every hour if a cert will expire within 5 days, and an ERROR every hour if we have 2 days left.

comment:4 Changed 7 years ago by karsten

I implemented most of your suggestions above. I couldn't distinguish between certs expiring within 14, 5, or 2 days, or at least not easily, so I just set the severity to WARNING.

comment:5 Changed 7 years ago by karsten

See the latest messages in #tor-bots and on the mailing list. Is this what you wanted? If so, can you close this ticket or tell me to do so?

comment:6 in reply to:  5 Changed 7 years ago by rransom

Resolution: implemented
Status: newclosed

Replying to karsten:

See the latest messages in #tor-bots and on the mailing list. Is this what you wanted?

It's good enough.

If so, can you close this ticket or tell me to do so?

Yes.

Note: See TracTickets for help on using tickets.