Skip to:

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

checkwmi don't work (WORKAROUND FOUND)

Description

I'm trying to setup wmi monitoring (as explained here http://www.opennms.org/wiki/WMI) but can't pass the checkwmi step.

My windows box seems to be correctly configured since a command like "wmic /user:xxxxx /password:jkdfsdkfj /node:10.8.0.18 process" works from my desktop.

But running the following command returns me the following result:

root@opennms:/usr/share/opennms/bin# ./checkwmi -matchType all -wmiClass Win32_BIOS -wmiObject Status -op EQ -value OK -domain . dsveiw Administrator 'password'
org.opennms.protocols.wmi.WmiException: Failed to establish COM session with host 'dsview.fw.belnet.be': Exception occurred. [0x80020009]
at org.opennms.protocols.wmi.WmiClient.connect(WmiClient.java:258)
at org.opennms.protocols.wmi.WmiManager.init(WmiManager.java:255)
at org.opennms.protocols.wmi.CheckWmi.main(CheckWmi.java:143)
Caused by: org.jinterop.dcom.impls.automation.JIAutomationException: Exception occurred. [0x80020009]
at org.jinterop.dcom.impls.automation.JIDispatchImpl.invoke(JIDispatchImpl.java:333)
at org.jinterop.dcom.impls.automation.JIDispatchImpl.callMethodA(JIDispatchImpl.java:520)
at org.jinterop.dcom.impls.automation.JIDispatchImpl.callMethodA(JIDispatchImpl.java:526)
at org.jinterop.dcom.impls.automation.JIDispatchImpl.callMethodA(JIDispatchImpl.java:477)
at org.opennms.protocols.wmi.WmiClient.connect(WmiClient.java:234)
... 2 more
Caused by: org.jinterop.dcom.common.JIRuntimeException: Exception occurred. [0x80020009]
at org.jinterop.dcom.core.JICallBuilder.readResult(JICallBuilder.java:1079)
at org.jinterop.dcom.core.JICallBuilder.read(JICallBuilder.java:957)
at ndr.NdrObject.decode(NdrObject.java:36)
at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:137)
at rpc.Stub.call(Stub.java:113)
at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:901)
at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:856)
at org.jinterop.dcom.core.JIComObjectImpl.call(JIComObjectImpl.java:266)
at org.jinterop.dcom.core.JIComObjectImpl.call(JIComObjectImpl.java:153)
at org.jinterop.dcom.impls.automation.JIDispatchImpl.invoke(JIDispatchImpl.java:315)
... 6 more

FLASH UPDATE: AAARGGHHHH THE FOLLOWING CHECKWMI COMMAND WORKS:

./checkwmi -matchType all -wmiClass Win32_BIOS -wmiObject Status -op EQ -value OK -domain . 10.8.0.18 Administrator 'password'
Checking: for Status Op: EQ Val: OK
Check results: OK (1)
Result for (1) Win32_BIOS\Status: OK
root@opennms:/usr/share/opennms/bin#

SO USING THE IP ADDRESS WORKS!!!!

Sorry for the uppercase I've spent hours trying to figure out the problem......

Environment

penNMS Version: 1.10.9-SNAPSHOT Home Directory: /usr/share/opennms RRD store by Group: false Web-Application Logfiles: /var/log/opennms/webapp Reports directory: /var/lib/opennms/reports Jetty http host: null Jetty http port: 80 Jetty https host: null Jetty https port: null System Configuration Server Time: Fri Mar 15 16:15:03 CET 2013 Client Time: Fri Mar 15 2013 16:15:04 GMT+0100 (Romance Standard Time) Java Version: 1.6.0_26 Sun Microsystems Inc. Java Virtual Machine: 20.1-b02 Sun Microsystems Inc. Operating System: Linux 2.6.32-5-amd64 (amd64) Servlet Container: jetty/7.5.1.v20110908 (Servlet Spec 2.5) User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alexander Hoogerhuis March 19, 2013 at 5:58 AM

When you use "-domain ." you access the local accounts, so it shouldn't matter if it is in a domain or not.

-A

Cyrille Bollu March 18, 2013 at 6:18 AM

_snd on IRC suggested that this issue would be caused by my Windows server's netbios name (WIN-01....) which doesn't match its DNS name (dsview). But, that's not the cause; We have changed our Windows server's netbios name as recommended, and the issue still occurs.

Maybe, it's because our server isn't part of a Windows domain (WORKGROUP)?

Cyrille

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created March 15, 2013 at 11:25 AM
Updated July 26, 2023 at 2:17 PM