OliverNickel
12 years agoNew Contributor
Unix Monitor not connecting
Connecting a monitor to our UNIX (IBM AIX) System is not working:
SNMP is working properly and is tested with SNMP Tester 5.1.2 from Paessler:
loadUI Pro Unix Monitor isnt able to connect as you see in the attached screenshot.
Which OIDs does loadUI Monitoring need to be published on the server? We followed the guideline from this URL http://www.loadui.org/Server-monitoring/unix-server-monitor.html
Issue has been reported in the Case #00030873 due to previous lack of permissions on the pro Forum.
best regards
Oliver
Connect/disconnect failed. Execution aborted.
org.codehaus.groovy.runtime.InvokerInvocationException: com.eviware.loadui.pro.api.monitoring.MonitorRequestException: Could not connect to server
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:97)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
at groovy.lang.Closure.call(Closure.java:412)
at com.eviware.loadui.util.groovy.GroovyEnvironment.invokeClosure(GroovyEnvironment.java:192)
at com.eviware.loadui.pro.impl.monitoring.groovy.GroovyMonitor.testConnection(Unknown Source)
at com.eviware.loadui.pro.impl.monitoring.snmp.d.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.eviware.loadui.pro.api.monitoring.MonitorRequestException: Could not connect to server
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:102)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:194)
at GroovycomeviwareloaduimonitorsNetSNMP$_run_closure1.doCall(GroovycomeviwareloaduimonitorsNetSNMP:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
at GroovycomeviwareloaduimonitorsNetSNMP$_run_closure1.doCall(GroovycomeviwareloaduimonitorsNetSNMP)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
... 13 more
Caused by: java.lang.RuntimeException: Request failed. Error [2: No such name] caugth on input value no. 1
at com.eviware.loadui.pro.impl.monitoring.snmp.SnmpSupportBase.a(Unknown Source)
at com.eviware.loadui.pro.impl.monitoring.snmp.SnmpSupportBase.get(Unknown Source)
at com.eviware.loadui.pro.impl.monitoring.snmp.GroovySnmpModule.get(Unknown Source)
at com.eviware.loadui.pro.impl.monitoring.snmp.GroovySnmpModule$get.call(Unknown Source)
at GroovycomeviwareloaduimonitorsNetSNMP$_run_closure1.doCall(GroovycomeviwareloaduimonitorsNetSNMP:91)
... 29 more
SNMP is working properly and is tested with SNMP Tester 5.1.2 from Paessler:
----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.2
26.03.2014 16:59:30 (2 ms) : Device: xxxxxxxxx
26.03.2014 16:59:30 (2 ms) : SNMP V1
26.03.2014 16:59:30 (3 ms) : Walk 1.3.6.1.2.1
26.03.2014 16:59:30 (16 ms) : 1.3.6.1.2.1.1.1.0 = "IBM PowerPC CHRP Computer
Machine Type: xxxxxxxxx Processor id: xxxxxxxxx
Base Operating System Runtime AIX version: 07.01.0002.0015
TCP/IP Client Support version: 07.01.0002.0015"
26.03.2014 16:59:30 (31 ms) : 1.3.6.1.2.1.1.2.0 = "1.3.6.1.4.1.2.3.1.2.1.1.3"
26.03.2014 16:59:30 (45 ms) : 1.3.6.1.2.1.1.3.0 = "517800"
26.03.2014 16:59:30 (59 ms) : 1.3.6.1.2.1.1.4.0 = ""
26.03.2014 16:59:30 (73 ms) : 1.3.6.1.2.1.1.5.0 = "xxxxxxxxx"
26.03.2014 16:59:30 (92 ms) : 1.3.6.1.2.1.1.6.0 = ""
26.03.2014 16:59:30 (106 ms) : 1.3.6.1.2.1.1.7.0 = "72"
26.03.2014 16:59:30 (121 ms) : 1.3.6.1.2.1.1.8.0 = "100"
26.03.2014 16:59:30 (135 ms) : 1.3.6.1.2.1.1.9.1.2.1 = "1.3.6.1.4.1.2.3.1.2.1.1.3"
26.03.2014 16:59:30 (150 ms) : 1.3.6.1.2.1.1.9.1.3.1 = "AIX SNMP Agent"
26.03.2014 16:59:30 (165 ms) : 1.3.6.1.2.1.1.9.1.4.1 = "100"
26.03.2014 16:59:30 (181 ms) : 1.3.6.1.2.1.11.1.0 = "295"
26.03.2014 16:59:30 (196 ms) : 1.3.6.1.2.1.11.3.0 = "0"
26.03.2014 16:59:30 (215 ms) : 1.3.6.1.2.1.11.4.0 = "0"
26.03.2014 16:59:30 (230 ms) : 1.3.6.1.2.1.11.5.0 = "0"
26.03.2014 16:59:30 (244 ms) : 1.3.6.1.2.1.11.6.0 = "0"
26.03.2014 16:59:30 (257 ms) : 1.3.6.1.2.1.11.30.0 = "2"
26.03.2014 16:59:30 (271 ms) : 1.3.6.1.2.1.11.31.0 = "0"
26.03.2014 16:59:30 (285 ms) : 1.3.6.1.2.1.11.32.0 = "0"
loadUI Pro Unix Monitor isnt able to connect as you see in the attached screenshot.
Which OIDs does loadUI Monitoring need to be published on the server? We followed the guideline from this URL http://www.loadui.org/Server-monitoring/unix-server-monitor.html
Issue has been reported in the Case #00030873 due to previous lack of permissions on the pro Forum.
best regards
Oliver