Skip to:

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

On opennms stop services on nodes that don't exist get discovered

Description

After digging into to this, I am seeing services discovered on nodes that don't
have those services. Oracle being discovered on Foundry switches,
VncJava(custom, tcp port 5800) being discovered on SCO server. Looking through
the poller log, it appears that this happens as opennms is going down(opennms.sh
stop). I will attach the snippet from poller.log that correlates to the bogus
VncJava discovery.

Environment

Operating System: Linux Platform: PC

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Show:

Ted Kaczmarek May 21, 2004 at 6:40 AM

Wahoo, passed with flying colors.
You the man. Mulitple restarts, rescans, and discoveries, not a single bogus
service discovered.

CVS from 5/19/04

Only thing I noticed is it appears that node rescans see to take longer than
they used to, never timed them though.

Regards,
Ted

David Hustace May 17, 2004 at 4:49 PM

Ted, can you check to see if this is still a problem? Matt believes that this maybe resolved now with the
new socket code.

Ted Kaczmarek April 13, 2004 at 7:55 PM

Matt, if you need anything with respect to this one please do ask.
Ted

Former user April 8, 2004 at 4:08 PM

Matt will need to reproduce and fix this one...

Ted Kaczmarek March 17, 2004 at 7:41 AM

This also happens when adding a node as well.

Ted

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

PagerDuty

Created February 21, 2004 at 8:06 AM
Updated January 27, 2017 at 4:31 PM
Resolved February 20, 2006 at 11:19 AM