AlertEngine Jabber plugin crashes on missing config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Medium
|
Thomas Adamcik |
Bug Description
As reported in bug 330426, AlertEngine will spew out error messages in its logs and via email when a plugin raises an unhandled exception.
The Jabber plugin will raise such an exception if a originating JID hasn't been configured in alertengine.conf:
[2009-02-17 09:24:59,224] [ERROR] [pid=15877 nav.alertengine] Unhandeled error from Jabber
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.connect()
File "/usr/lib/
self.jid = xmpp.protocol.
KeyError: 'jid'
Plugins should check their config at startup, and be disabled for the remainder of the process life if found to not be configured properly.
Changed in nav: | |
assignee: | nobody → adamcik |
importance: | Undecided → Medium |
milestone: | none → v3.5.1 |
status: | New → Confirmed |
Changed in nav: | |
status: | Confirmed → In Progress |
Changed in nav: | |
status: | Fix Committed → Fix Released |
See http:// metanav. uninett. no/hg/series/ 3.5.x/rev/ 099d8a97618c