All work
- Auto-ack with clear=true, send up notice for all unacked down noticesNMS-964Resolved issue: NMS-964OpenNMS Bug Mailing List
- Asset DB improvementNMS-960Resolved issue: NMS-960David Hustace
- Enhanced handling of service outages during node outagesNMS-952Resolved issue: NMS-952OpenNMS Bug Mailing List
- The <switch> and <substitution> tags in notificationCommands are backwardsNMS-947Resolved issue: NMS-947
- Umbrella Bug for Path OutageNMS-939
- Make the categories in assets soft-codedNMS-938
- SNMP data collection hung threadsNMS-925Resolved issue: NMS-925OpenNMS Bug Mailing List
- eventd stuck in start state when loading new events.xml fileNMS-919Resolved issue: NMS-919OpenNMS Bug Mailing List
- when add a new node, it added as an interface of another existing nodeNMS-916Resolved issue: NMS-916OpenNMS Bug Mailing List
- Java reporting annoyancesNMS-908Resolved issue: NMS-908Tarus Balog
- Viewing Event in Web UINMS-906Resolved issue: NMS-906Tarus Balog
- Installation or upgrade should not automatically restart postgresqlNMS-899Resolved issue: NMS-899Eric Evans
- This Bug Blocks the 1.2 ReleaseNMS-889Resolved issue: NMS-889Tarus Balog
- Install document needs to be updatedNMS-886Resolved issue: NMS-886Tarus Balog
- Newly discovered nodes only partially added to db when SNMP is enabledNMS-884Resolved issue: NMS-884Eric Evans
- RTC not aware of deleted nodesNMS-881Resolved issue: NMS-881OpenNMS Bug Mailing List
- Throws exception when issuing a node rescanNMS-870Resolved issue: NMS-870OpenNMS Bug Mailing List
- Too many open files (problems running on 1.4.2?)NMS-868Resolved issue: NMS-868OpenNMS Bug Mailing List
- Create an SSH poller (improving on the current one which causes DoS)NMS-866Resolved issue: NMS-866OpenNMS Bug Mailing List
- total in/out bits added to "Bits In/Out" reportNMS-865Resolved issue: NMS-865Tarus Balog
- lynx -source http://install.opennms.org|sh responds with sh: line 1: !DOCTYPE: No such file or directoryNMS-864Resolved issue: NMS-864Tarus Balog
- Cisco Traps doesn't workNMS-862Resolved issue: NMS-862Tarus Balog
- Not able to loginNMS-857Resolved issue: NMS-857Tarus Balog
- build.xml uses unsupported linker flag on linuxNMS-854Resolved issue: NMS-854Tarus Balog
- discovery not completing, send-event.pl not working on bad range eitherNMS-852Resolved issue: NMS-852OpenNMS Bug Mailing List
- Configuration files get "contaminated"NMS-851Resolved issue: NMS-851Tarus Balog
- split snmp-graph.propertiesNMS-850Resolved issue: NMS-850Alejandro Galue
- expanded use of include files.NMS-849Resolved issue: NMS-849Tarus Balog
- KSC Reports cause NullPointer ExceptionNMS-848Resolved issue: NMS-848Tarus Balog
- Add ifAlias to Performance Report displayNMS-586Resolved issue: NMS-586Tarus Balog
30 of 30
Auto-ack with clear=true, send up notice for all unacked down notices
Duplicate
Description
Environment
Operating System: All
Platform: All
Acceptance / Success Criteria
None
Attachments
1
duplicates
Lucidchart Diagrams
Details
Assignee
OpenNMS Bug Mailing ListOpenNMS Bug Mailing ListReporter
Craig MiskellCraig MiskellComponents
Fix versions
Affects versions
Priority
Minor
Details
Details
Assignee
OpenNMS Bug Mailing List
OpenNMS Bug Mailing ListReporter
Craig Miskell
Craig MiskellComponents
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created July 14, 2004 at 3:54 PM
Updated January 27, 2017 at 4:32 PM
Resolved February 20, 2006 at 11:19 AM
Activity
Craig MiskellJuly 15, 2004 at 3:32 PM
Dammit - forgot that I'd already submitted this patch for https://opennms.atlassian.net/browse/NMS-818#icft=NMS-818. Please
ignore me, I went on holiday and left my brain behind when i cam back.
This bug has been marked as a duplicate of 731 ***
Craig MiskellJuly 14, 2004 at 3:55 PM
Created an attachment (id=95)
Described patch
Against 1.1.2 or so, not CVS. Sorry
Currently, if
1) a "down" notification is sent
2) there is an auto-ack on the down/up pair, and clear=true so that the up will
also be acked
3) the "up" event occurs before the down is acknowledged
then the user will receive the down notice, but never receive an up notice.
With this patch, when clear=true on an auto-acknowledgement, an "up/regained"
notification is sent to all users who received a "down/lost" notification and
who haven't yet acknowledged the "down/lost" notification.