Skip to:

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

collectd.log

Description

2012-04-10 10:46:43,802 WARN [CollectdScheduler-50 Pool-fiber0] CollectionResourceWrapper: getAttributeValue: can't find attribute called avgBusy5 on node[30]
2012-04-10 10:46:58,755 WARN [CollectdScheduler-50 Pool-fiber0] CollectionResourceWrapper: getAttributeValue: can't find attribute called avgBusy5 on node[39]
2012-04-10 10:47:30,749 WARN [CollectdScheduler-50 Pool-fiber0] CollectableService: run: failed collection for 172.16.5.106/SNMP/example1
2012-04-10 10:47:30,749 ERROR [CollectdScheduler-50 Pool-fiber0] CollectableService: Timeout retrieving SnmpCollectors for 172.16.5.106 for /172.16.5.106: SnmpCollectors for 172.16.5.106: snmpTimeoutError for: /172.16.5.106
org.opennms.netmgt.collectd.CollectionTimedOut: Timeout retrieving SnmpCollectors for 172.16.5.106 for /172.16.5.106: SnmpCollectors for 172.16.5.106: snmpTimeoutError for: /172.16.5.106
at org.opennms.netmgt.collectd.SnmpCollectionSet.verifySuccessfulWalk(SnmpCollectionSet.java:369)
at org.opennms.netmgt.collectd.SnmpCollectionSet.collect(SnmpCollectionSet.java:394)
at org.opennms.netmgt.collectd.SnmpCollector.collect(SnmpCollector.java:349)
at org.opennms.netmgt.collectd.CollectionSpecification.collect(CollectionSpecification.java:267)
at org.opennms.netmgt.collectd.CollectableService.doCollection(CollectableService.java:366)
at org.opennms.netmgt.collectd.CollectableService.run(CollectableService.java:300)
at org.opennms.netmgt.scheduler.LegacyScheduler$1.run(LegacyScheduler.java:287)
at org.opennms.core.concurrent.RunnableConsumerThreadPool$FiberThreadImpl.run(RunnableConsumerThreadPool.java:420)
at java.lang.Thread.run(Thread.java:722)

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger July 30, 2012 at 5:04 PM

Seems like expected behavior, closing issue.

Benjamin Reed May 2, 2012 at 10:42 AM

Do you have a particular problem here that I'm not seeing? This seems normal; collectd tried to connect to 172.16.5.106 and it timed out. Have you done any troubleshooting on your connection to that node?

Configuration

Details

Assignee

Reporter

Components

Affects versions

Due date

Priority

PagerDuty

Created April 10, 2012 at 4:53 AM
Updated July 30, 2012 at 5:05 PM
Resolved July 30, 2012 at 5:04 PM