3.5 sql upgrade script does not flush old alerts from db
Bug #298039 reported by
Thomas Adamcik
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Network Administration Visualized |
Fix Released
|
High
|
Unassigned | ||
| 3.5 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
The old database structure has a table that keeps track of what the newest handled alert is, in normal operation all alerts with a smaller id are deleted. However in a certain debug mode this is not done, resulting in the new alertengine code seeing a ton of old alerts as new ones to be handled.
DELETE FROM alertq WHERE id < (SELECT .... ); should do the trick
| Changed in nav: | |
| importance: | Undecided → High |
| milestone: | none → v3.5.0 |
| status: | New → Confirmed |
| Changed in nav: | |
| milestone: | v3.5.0b3 → none |
Revision history for this message
| Thomas Adamcik (adamcik) wrote | #1 |
| Changed in nav: | |
| status: | Confirmed → Fix Committed |
| Changed in nav: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
http://