OpenNMS

newSuspect event does not match notice

Details

  • Type: Bug Bug
  • Status: Reopened Reopened
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.3.0
  • Fix Version/s: 1.11.91
  • Component/s: Notifications/Actions
  • Security Level: Default (Default Security Scheme)
  • Labels:
    None
  • Environment:
    Operating System: All
    Platform: All
  • Bugzilla Id:
    1371

Description

I added a notification based on the newSuspect event (uei.opennms.org/internal/discovery/newSuspect).
The notice was created correctly, but when the event is generated it logs that the event does not match a
notice.

For my example, nodeid = 0, ipaddr = 10.1.1.1, service = null

I think the nodeid of 0 is what is causing the issue. This has happened before.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. NMS-1276 Notifications don't work if IP is not in database

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tarus Balog added a comment -

Created an attachment (id=258)
A test for this problem

patch from mhuot

Show
Tarus Balog added a comment - Created an attachment (id=258) A test for this problem patch from mhuot
Hide
Permalink
Mike Huot added a comment -

Test and fix submitted to HEAD

Show
Mike Huot added a comment - Test and fix submitted to HEAD
Hide
Permalink
Mike Huot added a comment -
      • NMS-1276 has been marked as a duplicate of this bug. ***
Show
Mike Huot added a comment - NMS-1276 has been marked as a duplicate of this bug. ***
Hide
Permalink
Tarus Balog added a comment -

Okay, with the introduction of provisiond, some people would like to be notified on newSuspect events. However, OpenNMS will not allow a notice to match unless the node or IP associated with the event is in the database. For example, if the IP in the newSuspect is 1.2.3.4:

rule "(((ipaddr iplike ...)) & (ipAddr
== '1.2.3.4'))" does not match an entry in the database

Unfortunately, even an empty rule fails:

SQL Exception occurred
testing rule "(() & (ipAddr == '1.2.3.4'))" for matching results:
org.postgresql.util.PSQLException: ERROR: syntax error at or near ")"

I could not think of a rule that would cause this notice to be sent, since it requires one and rules only exist to return a list of IPs from the DB. Since the IP isn't in the DB - no love.

Show
Tarus Balog added a comment - Okay, with the introduction of provisiond, some people would like to be notified on newSuspect events. However, OpenNMS will not allow a notice to match unless the node or IP associated with the event is in the database. For example, if the IP in the newSuspect is 1.2.3.4: rule "(((ipaddr iplike . . . )) & (ipAddr == '1.2.3.4'))" does not match an entry in the database Unfortunately, even an empty rule fails: SQL Exception occurred testing rule "(() & (ipAddr == '1.2.3.4'))" for matching results: org.postgresql.util.PSQLException: ERROR: syntax error at or near ")" I could not think of a rule that would cause this notice to be sent, since it requires one and rules only exist to return a list of IPs from the DB. Since the IP isn't in the DB - no love.

People

  • Assignee:
    Matt Brozowski
    Reporter:
    Tarus Balog
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: