snmpcollector 2.x stops collecting data

Document ID : KB000057306
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms


A device is discovered correctly in snmpcollector but stops being polled after a period of time.

Examining the pollagent log show the following errors repeating frequently.
[Info.] (Tests:SnmpGetExpression:p_192.168.168.168|NormalizedAvailabilityInfo|s1) 192.168.168.168_snmpv3nimsoft - 192.168.168.168_snmpv3nimsoft - INFO: RESPONSE_OID: sysUpTime 1.3.6.1.2.1.1.3.0 = 4036947760
[Error] Exception in thread "Thread-221"?
[Error] java.lang.NoSuchMethodError: com.nimsoft.probes.metricfamily.expression.ExpressionEvaluator.getVariables()Ljava/util/Set;
[Error] ? at com.firehunter.agent.snmp.SnmpGetExpressionTest.fixUnresolvedVars(SnmpGetExpressionTest.java:1046)

Finally, at the end of the log file the following error may be the only entry being made:
[Warn.] ######################### WARNING: REPORT TEST MUST HAVE STOPPED - LAST CLEAR TIME HAS BEEN OVER 30 min. !!!

*Note: The pollagent log does not follow the standard UIM log naming scheme. ?It can be found in the following location:?Nimsoft\probes\network\pollagent\log\AGM.log






Solution


This issue can occur after a system has been upgraded from a pre 2.0 version of snmpcollector.

For example, migrating from NMS 7.6 to UIM 8.1.

The solution is to:
  1. Remove the pollagent probe from Infrastructure Manager or Admin Console
  2. Remove the pollagent folder from the robot
  3. Redeploy the newest pollagent from the archive