Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-3882

Case sensitive inconsistency between capsd and poller for HostResourceSwRunMonitor

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.6.10
    • 1.9.4
    • Security Level: Default (Default Security Scheme)
    • None
    • Operating System: Linux
      Platform: All
    • 3838

    Description

      When monitoring using HostResourceSwRunMonitor, a service will be detected by capsd in a case-insensitive fashion, but the poller will look for it in a case-sensitive fashion.

      Example:

      Monitoring a process on a host called 'OmniTek XR.exe'. My original capsd-configuration.xml definition looked like this:

      – cut –
      <protocol-plugin protocol="Omnitek-Scope" class-name="org.opennms.netmgt.capsd.plugins.HostResourceSwRunPlugin" scan="on" user-defined="false">
      <property key="timeout" value="3000" />
      <property key="retry" value="1" />
      <property key="service-name" value="Omnitek XR.exe" />
      </protocol-plugin>
      – cut –

      which detected the service and registered it with nodes where it was found running.

      Using similar attributes in poller-configuration.xml, it was flagged as down for reason 'Unknown' by the poller when using this definition:

      – cut –
      <service name="Omnitek-Scope" interval="300000" user-defined="false" status="on">
      <parameter key="retry" value="1"/>
      <parameter key="timeout" value="10000"/>
      <parameter key="service-name" value="Omnitek XR.exe"/>
      </service>

      Correcting the case in poller-configuration.xml to match the actual application image name "OmniTek XR.exe" causes polling to correctly detect the application once more, but capsd and poller should detect applications using the same text matching rules.

      Attachments

        Activity

          People

            seth Seth Leger
            klaus-s@moving-picture.com klaus-s (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: