Bug #12282

Monitoring of *.lizard is broken

Added by intrigeri 2017-03-03 20:00:50 . Updated 2017-03-08 14:03:44 .

Status:
Resolved
Priority:
High
Assignee:
intrigeri
Category:
Infrastructure
Target version:
Tails_2.12
Start date:
2017-03-03
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

… except monitoring of monitor.lizard. Seems that I broke it on Feb 15. bertagaz said he would take care of it, but if that doesn’t happen soon I should take over and fix my mistakes.

Subtasks

History

#1 Updated by intrigeri 2017-03-08 09:02:27

  • Target version changed from Tails_2.11 to Tails_2.12

#2 Updated by bertagaz 2017-03-08 11:07:22

  • Status changed from Confirmed to In Progress
  • Assignee changed from bertagaz to intrigeri
  • QA Check set to Info Needed

I’ve enabled back the monitoring setup as it was before the changes on February 15, so it’s back on track.

Now I’m trying to understand if the monitoring of this host is broken and get some evidence of it. Looking at its history, it seems there were check failures happening in the past (see https://icingaweb2.tails.boum.org/monitoring/list/eventhistory?host_name=monitor.lizard&limit=100&modifyFilter=1) e.g on January 15 but maybe I’m misunderstanding something. Maybe we can do some test to check if it’s broken, like avoiding to update this host and see if we get some reports from its APT check?

#3 Updated by intrigeri 2017-03-08 14:03:44

  • Status changed from In Progress to Resolved

I was probably mis-remembering or something. I’ll file a new ticket next time I notice a problem.