AlertEngine mailbombs: AlertQueueMessage matching query does not exist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
High
|
Thomas Adamcik |
Bug Description
AlertEngine on a NAV 3.5.2 installation kept mailbombing us with the following traceback:
[2009-03-23 09:28:27,018] [ERROR] [pid=23987 nav.alertengine
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
return self.handler_
File "/usr/lib/
message = alert.messages.
File "/var/lib/
return self.get_
File "/var/lib/
raise self.model.
DoesNotExist: AlertQueueMessage matching query does not exist.
A similar traceback is also mailed for the Email handler.
Previous experience indicates that this error may appear when accountalertqueue records refer to non-existant alertq records. Inspection of the database reveals that this is not the case here.
When AlertEngine was restarted, the mailbombing stopped, as it began blacklisting the handlers instead (as the above traceback shoiws). But the effect of this is that no alerts are sent whatsoever.
Changed in nav: | |
assignee: | nobody → adamcik |
importance: | Undecided → High |
Changed in nav: | |
status: | New → In Progress |
Changed in nav: | |
milestone: | none → v3.5.3 |
Changed in nav: | |
status: | Fix Committed → Fix Released |
Could the problem be that there are no entries in the alertqmsg table for the alert that is being attempted dispatched?
I see no other choice to resolve this situation than by removing the accountalertqueue entries forcefully.