Unable to find device

ElastiFlow Community
1

Has anyone figure out yet what the root cause of this issue? I can snmpwalk on my cisco device and this is my devices.yml

enterprise:
  ip: 10.1.0.10
  port: 161
  version: 2c
  communities:
    - public
  device_groups:
    - cisco_generic

ERROR

Jul 16 14:12:49 elastiflow snmpcoll[9695]: {"level":"error","ts":"2025-07-16T14:12:49.080+1200","logger":"snmpcoll.snmp.controller","caller":"controller/controller.go:302","msg":"unable to find device details","ip":"10.1.0.10","port":161,"stacktrace":"github.com/elastiflow/flowcoll/pkg/inputs/snmp/controller.applyControlSignalDeviceAdd\n\t/tmp/collectors/pkg/inputs/snmp/controller/controller.go:302\ngithub.com/elastiflow/flowcoll/pkg/inputs/snmp/controller.(*Controller).handleControlStream\n\t/tmp/collectors/pkg/inputs/snmp/controller/controller.go:280\ngithub.com/elastiflow/flowcoll/pkg/inputs/snmp/controller.(*Controller).Run\n\t/tmp/collectors/pkg/inputs/snmp/controller/controller.go:186"}
Jul 16 14:12:49 elastiflow snmpcoll[9695]: panic: runtime error: invalid memory address or nil pointer dereference
Jul 16 14:12:49 elastiflow snmpcoll[9695]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x9c pc=0xb4daf7]
Jul 16 14:12:49 elastiflow snmpcoll[9695]: goroutine 163 [running]:
Jul 16 14:12:49 elastiflow snmpcoll[9695]: github.com/elastiflow/flowcoll/pkg/inputs/snmp/opmanager.(*OpManager).forwardOperationsForDevice(0xc0015364d0, {0x20fdfb0, 0xc0015ec000}, 0xc0025a0c60, {{0xc0016a01e2, 0x9}, 0xa1}, 0xc0020ae000)
Jul 16 14:12:49 elastiflow snmpcoll[9695]:         /tmp/collectors/pkg/inputs/snmp/opmanager/opmanager.go:150 +0x237
Jul 16 14:12:49 elastiflow snmpcoll[9695]: created by github.com/elastiflow/flowcoll/pkg/inputs/snmp/opmanager.(*OpManager).captureControlSignal in goroutine 137
Jul 16 14:12:49 elastiflow snmpcoll[9695]:         /tmp/collectors/pkg/inputs/snmp/opmanager/opmanager.go:119 +0x6d6
Jul 16 14:12:49 elastiflow systemd[1]: snmpcoll.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 16 14:12:49 elastiflow systemd[1]: snmpcoll.service: Failed with result 'exit-code'.
Jul 16 14:12:49 elastiflow systemd[1]: snmpcoll.service: Consumed 2.168s CPU time.
Jul 16 14:12:49 elastiflow systemd[1]: snmpcoll.service: Scheduled restart job, restart counter is at 2.
Jul 16 14:12:49 elastiflow systemd[1]: Stopped ElastiFlow SNMP Collector.
Jul 16 14:12:49 elastiflow systemd[1]: snmpcoll.service: Consumed 2.168s CPU time.
Jul 16 14:12:49 elastiflow systemd[1]: Started ElastiFlow SNMP Collector.

iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.9.1.1041
iso.3.6.1.2.1.1.3.0 = Timeticks: (1253077) 3:28:50.77
iso.3.6.1.2.1.1.4.0 = STRING: "\"admin@yourcompany.com\""
iso.3.6.1.2.1.1.5.0 = STRING: "Management-Router"
iso.3.6.1.2.1.1.6.0 = STRING: "\"Your Data Center\""
iso.3.6.1.2.1.1.7.0 = INTEGER: 78
iso.3.6.1.2.1.1.8.0 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.1.9.1.2.1 = OID: iso.3.6.1.4.1.9.7.129
2

Here’s the fix which I found from another post

rm -rf /usr/share/elastiflow/snmpcoll/*.gob

3

Glad you found a fix!

We will be making some changes around the “persist” feature that creates that object file.

Regards,
Dexter Turner

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.