capsd-configuration being overwritten

Description

I made the following entry within capsd-configuration:

<protocol-plugin protocol="NSClient" class-name="org.opennms.netmgt.capsd.plugins.NsclientPlugin" scan="on" user-defined="false">
<property key="banner" value="*" />
<property key="port" value="1248" />
<property key="timeout" value="3000" />
<property key="retry" value="2" />
</protocol-plugin>

Had OpenNMS discover a host with the NSClient loaded, the service was detected and added to the UI as 'not discovered. (everything is fine thus far)

However, if I go into Admin --> Configure Pollers --> Add Customer Poller and click 'Cancel'... all of the NSClient information (from above) is erased from capsd-configuration... or, it actually appears as if capsd-configuration is being overwritten with the default file.

It's odd, but despite the entry being removed from capsd-config, OpenNMS does continue to scan for this service, on this node, when rescanned.

I hope that made sense . I had this conversation on IM with joed.

Environment

Operating System: Linux Platform: All

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Tarus Balog October 30, 2007 at 9:33 AM

We have removed the Configure Pollers Admin item for now as it needs to be totally rewritten.

Tarus Balog May 22, 2007 at 1:26 PM

If you manually change the capsd configuration file you have to restart both opennms and tomcat, as tomcat stores a cached copy.

We should re-read the file if changed before commiting it, but that's the workaround.

Won't Fix

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created May 21, 2007 at 9:18 PM
Updated January 27, 2017 at 4:31 PM
Resolved October 30, 2007 at 9:33 AM