-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Meridian-2018.1.7
-
Fix Version/s: Meridian-2018.1.14, Meridian-2019.1.1, 25.1.1
-
Component/s: OSGi, Polling / Monitors / Outages
-
Security Level: Default (Default Security Scheme)
-
Sprint:Horizon 2019 - October 30th, Horizon 2019 - November 6th, Horizon 2019 - November 13th
I'm studying the possibility of using WS-Man instead of SNMP to check the status of Windows Services from Windows Servers.
While I was doing that, I found a problem with the execution of the poller:poll command from the Karaf Shell when trying to run the WsManMonitor on a device behind a location:
admin@opennms> poller:poll -l Singapore org.opennms.netmgt.poller.monitors.SnmpMonitor 10.22.5.57
Service is Up on 10.22.5.57 using org.opennms.netmgt.poller.monitors.SnmpMonitor:
response-time: 2.8149
admin@opennms> poller:poll -l Singapore org.opennms.netmgt.poller.monitors.WsManMonitor 10.22.5.57 resource-uri=http://s
chemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_Service selector.Name=MSSQLSERVER rule="#State matches 'Running'
and #Status matches 'OK'"
Service is Unknown on 10.22.5.57 using org.opennms.netmgt.poller.monitors.WsManMonitor
Reason: Unable to return specified BeanFactory instance: factory key [daoContext], from group with resource name [classpath*:beanRefContext.xml]; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'daoContext' is defined
This environment is running Meridian 2018, and WS-Man is configured with basic authentication.
- is duplicated by
-
-
- Resolved
-
