commit 19a57c6a0987f92b5d2704b7b19b42c86876b047 Author: Karsten Loesing karsten.loesing@gmx.net Date: Mon Mar 14 14:53:44 2011 +0100
Having no recent consensus probably means we're in trouble. --- .../ernie/cron/ConsensusHealthChecker.java | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/org/torproject/ernie/cron/ConsensusHealthChecker.java b/src/org/torproject/ernie/cron/ConsensusHealthChecker.java index 65a8cce..602d030 100644 --- a/src/org/torproject/ernie/cron/ConsensusHealthChecker.java +++ b/src/org/torproject/ernie/cron/ConsensusHealthChecker.java @@ -87,7 +87,7 @@ public class ConsensusHealthChecker { * with a warning, because we might just not have learned about a new * consensus in this execution. */ if (this.mostRecentConsensus == null) { - nagiosUnknowns.add("No consensus known"); + nagiosCriticals.add("No consensus known"); return; }