Skip to:

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

NPE in IcmpMonitor

Description

I just performed the upgrade (to ONMS 1.5.90) based on the MOP provided
and the sql instructions below. The software is all upgraded and running
but it looks like there may be an issue with the Icmp monitor. I am
seeing lots of entries in the pollers.log like the following:

2008-03-27 11:01:35,393 DEBUG [PollerScheduler-30 Pool-fiber28]
IcmpMonitor: failed to ping /10.63.252.114
java.lang.NullPointerException at org.opennms.netmgt.poller.monitors.IcmpMonitor.poll(IcmpMonitor.java:123) at org.opennms.netmgt.poller.pollables.LatencyStoringServiceMonitorAdaptor.poll(LatencyStoringServiceMonitorAdaptor.java:90) at org.opennms.netmgt.poller.pollables.PollableServiceConfig.poll(PollableServiceConfig.java:100) at org.opennms.netmgt.poller.pollables.PollableService.poll(PollableService.java:143) at org.opennms.netmgt.poller.pollables.PollableElement.poll(PollableElement.java:158) at org.opennms.netmgt.poller.pollables.PollableContainer$4.run(PollableContainer.java:201) at org.opennms.netmgt.poller.pollables.PollableElement.withTreeLock(PollableElement.java:143) at org.opennms.netmgt.poller.pollables.PollableElement.withTreeLock(PollableElement.java:135) at org.opennms.netmgt.poller.pollables.PollableContainer.poll(PollableContainer.java:208) at org.opennms.netmgt.poller.pollables.PollableInterface.poll(PollableInterface.java:142) at org.opennms.netmgt.poller.pollables.PollableContainer$4.run(PollableContainer.java:201) at org.opennms.netmgt.poller.pollables.PollableElement.withTreeLock(PollableElement.java:143)

...

Environment

Operating System: All Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Former user April 21, 2008 at 5:39 PM

merged to 1.6 branch in revision 8970

Benjamin Reed March 27, 2008 at 3:29 PM

this seems to work, and should do the right thing when getting a null entry, marking as fixed

Benjamin Reed March 27, 2008 at 1:36 PM

I've got a potential fix committed to the 1.6-testing branch in r8807; I'm working on getting it to the customer to see if this solves the issue for them.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created March 27, 2008 at 1:34 PM
Updated January 27, 2017 at 4:25 PM
Resolved April 30, 2008 at 3:42 PM

Flag notifications