Nagios check goes UNKNOWN when check-failed
Bug #1778447 reported by
William Grant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Livepatch Charm |
Fix Released
|
Medium
|
Barry Price |
Bug Description
check_canonical
$ /usr/lib/
Check failed
<function check_status at 0x7f6050841b90> raised unknown exception '<type 'exceptions.
=======
Traceback (most recent call last):
File "/usr/lib/
function(*args, **kwargs)
File "/usr/lib/
sys.exit(2)
SystemExit: 2
=======
$ echo $?
3
Related branches
~barryprice/charm-canonical-livepatch/+git/canonical-livepatch-charm:master
Merged
into
~livepatch-charmers/charm-canonical-livepatch:master
at
revision 6f5d8fcb8a026e3fa48f0c4cd3de20e14e41db97
- Livepatch charm developers: Pending requested
-
Diff: 49 lines (+6/-9)1 file modifiedfiles/check_canonical-livepatch.py (+6/-9)
~barryprice/charm-canonical-livepatch/+git/canonical-livepatch-charm:lp1778447
Merged
into
~livepatch-charmers/charm-canonical-livepatch:master
at
revision 62884614f807ca2fc1a32cfa4b02161c6d9a5ced
- Gareth Woolridge: Approve
- Barry Price: Approve
-
Diff: 49 lines (+9/-6)1 file modifiedfiles/check_canonical-livepatch.py (+9/-6)
~barryprice/charm-canonical-livepatch/+git/canonical-livepatch-charm:lp1778447
Merged
into
~livepatch-charmers/charm-canonical-livepatch:master
at
revision 5a22e593df257a2302a1dd7395675e35f0fcb7dc
- Paul Gear (community): Approve
-
Diff: 49 lines (+6/-9)1 file modifiedfiles/check_canonical-livepatch.py (+6/-9)
Changed in canonical-livepatch-charm: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Barry Price (barryprice) |
Changed in canonical-livepatch-charm: | |
status: | Triaged → In Progress |
Changed in canonical-livepatch-charm: | |
status: | In Progress → Fix Committed |
Changed in canonical-livepatch-charm: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Related to LP: #1744092 where service is unavailable. I think this plugin should handle it better and keep it critical rather than unknown.
|12:59 <wgrant> I've just had a dozen or so units show up with livepatch check failures /livepatch. canonical. com/api/ machine/ aca1b9797a4143a dbfdd1da59c4468 f4 /h1>#012The server didn't respond in /body>< /html>
|13:00 <wgrant> Shows up as UNKNOWN in nagios for some reason, but:
|13:00 <wgrant> Bad server status code: 504. URL: https:/
<html><body><h1>504 Gateway Time-out<
time.#012<