Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Reasons Missing From nodeLostService events

Description

When I demo OpenNMS, I usually stop and start "httpd" to cause a service outage. Today I noticed that instead of getting a "could not connect to port 80" reason I got Unknown:

HTTP outage identified on interface 172.20.1.11 with reason code: Unknown.

Methinks this be broky.

1.7.91-SNAPSHOT

Environment

Operating System: All Platform: All

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Martin Lärcher May 16, 2012 at 2:02 PM

Also SNMP-Monitor in 1.10.2:
SNMP-Fans outage identified on interface x.x.x.x with reason code: Unknown.
Because SNMP is down on node (stopped) it would be nice if i get an unresponsive response and avoid notification

Ryan Ruuska March 6, 2012 at 11:42 AM

Furthermore, HTTP is not down on the node and although it is slow, it is within the timeout value and should not be reported as down.

Ryan Ruuska March 6, 2012 at 11:34 AM

I'm running 1.10.0-2, no info on HTTP outages.

HTTP outage identified on interface xxx.xxx.16.34 with reason code: Unknown.

Seth Leger December 6, 2011 at 3:13 PM

The HttpMonitor portion of this was a duplicate of bug and I've also fixed the DhcpMonitor by using a similar catch(Throwable) statement. Marking as fixed.

commit 2ccf2a5fe50b35c359d528836af6eb5a6a0f5044
commit 1a5457add292236b37ed5af596b27c9d2baba420

Eric W Abrahamsen October 20, 2011 at 9:18 PM

Also HTTP.

HTTP outage identified on interface 172.16.x.x with reason code: Unknown.

Fixed

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created May 27, 2010 at 5:40 PM
Updated October 29, 2021 at 9:39 PM
Resolved October 29, 2021 at 9:37 PM