Comments (14)
Recompiled to newest version 1.1.28. The problem still exists. If I change to php poller the problem partly disappers.
from spine.
Tried to readd graph:
2017-12-07 15:50:03 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194306560), Set MAX_OIDS to 1 for this host to isolate bad OID
2017-12-07 15:50:03 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10457] SNMP: v2: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306560, value: U
2017-12-07 15:50:03 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194306560), Set MAX_OIDS to 1 for this host to isolate bad OID
2017-12-07 15:50:03 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10457] SNMP: v2: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306560, value: U
2017-12-07 15:50:03 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194304000), Set MAX_OIDS to 1 for this host to isolate bad OID
2017-12-07 15:50:03 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10447] SNMP: v2: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304000, value: U
Doesn't work.
The host is OLT - Huawei MA5608T.
from spine.
Can you please upload an tcpdump of polling just this host?
tcpdump -w /tmp/spine_capture.pcap &
./spine -R -f 666 -l 666
It's essential to have the tcpdump. Thanks!
from spine.
LOG FROM CONSOLE:
SPINE: Using spine config file [/etc/cacti/spine.conf] SPINE: Version 1.1.28 starting 2018-01-04 14:53:12 - SPINE: Poller[1] DEBUG: In Poller, About to Start Polling of Device for Device ID 666 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] DEBUG: Entering UDP Ping 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] DEBUG: UDP Device Alive, Try Count:1, Time:1.4138 ms 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] DEBUG: Entering SNMP Ping 2018-01-04 14:53:12 - SPINE: Poller[1] Updating Full System Information Table 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] RECACHE: Processing 1 items in the auto reindex cache for '10.200.0.223' 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] Recache DataQuery[1] OID: .1.3.6.1.2.1.1.3.0, output: 4941565 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] NOTE: There are '35' Polling Items for this Device 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194306048), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10455] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306048, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10455] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306048, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194306304), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10456] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306304, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10456] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306304, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194306304), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10456] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306304, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10456] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306304, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194305280), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10452] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305280, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10452] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305280, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194306048), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10455] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306048, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10455] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306048, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194305792), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10454] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305792, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10454] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305792, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194305792), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10454] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305792, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10454] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305792, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194305536), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10453] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305536, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10453] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305536, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194305536), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10453] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305536, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10453] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305536, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194305280), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10452] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305280, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10452] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305280, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194305024), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10451] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305024, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10451] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305024, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194304512), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10449] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304512, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10449] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304512, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194304512), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10449] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304512, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10449] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304512, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194304256), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10448] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304256, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10448] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304256, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194304256), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10448] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304256, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10448] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304256, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194304768), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:12 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10450] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304768, value: U 2018-01-04 14:53:12 - SPINE: Poller[1] Device[666] TH[1] DS[10450] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304768, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194305024), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10451] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305024, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10451] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305024, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194304768), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10450] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304768, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10450] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304768, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] DEBUG: The NIFTY POPEN returned the following File Descriptor 7 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10442] SCRIPT: perl /var/www/html/cacti/scripts/ping.pl '10.200.0.223', output: 1.29 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194307840), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10462] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194307840, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10462] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194307840, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10446] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.234946560, value: 19323757927897 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194307584), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10461] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194307584, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10461] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194307584, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194307584), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10461] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194307584, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10461] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194307584, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194307840), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10462] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194307840, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10462] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194307840, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194307328), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10460] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194307328, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10460] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194307328, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194307328), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10460] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194307328, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10460] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194307328, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194307072), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10459] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194307072, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10459] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194307072, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194307072), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10459] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194307072, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10459] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194307072, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194306816), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10458] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306816, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10458] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306816, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10446] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.234946560, value: 257403667162547 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194304000), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10447] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304000, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10447] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304000, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194306816), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10458] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306816, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10458] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306816, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194306560), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10457] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306560, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10457] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194306560, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.6.4194306560), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10457] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306560, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10457] SNMP: v1: 10.200.0.223, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194306560, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.31.1.1.1.10.4194304000), Set MAX_OIDS to 1 for this host to isolate bad OID 2018-01-04 14:53:13 - SPINE: Poller[1] WARNING: Invalid Response, Device[666] TH[1] DS[10447] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304000, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DS[10447] SNMP: v1: 10.200.0.223, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304000, value: U 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] Total Time: 1.7 Seconds 2018-01-04 14:53:13 - SPINE: Poller[1] Device[666] TH[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function 2018-01-04 14:53:13 - SPINE: Poller[1] DEBUG: The Value of Active Threads is 0 for Device ID 666 SPINE: Time: 2.0275 s, Threads: 24, Devices: 1
Can I send You pcap by mail?
from spine.
Send to [email protected] please.
from spine.
Please try again with the latest commit. The reason for the issue is that the OID index was too large (aka '4194304000' is too high). Close if resolved.
from spine.
On all OLTs the graphs are now OK but problem still exists on one specified OLT:
# spine -f 566 -l 566
SPINE: Using spine config file [/etc/cacti/spine.conf]
SPINE: Version 1.1.30 starting
2018/01/05 12:50:32 - SPINE: Poller[1] DEBUG: In Poller, About to Start Polling of Device for Device ID 566
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] DEBUG: Entering UDP Ping
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] DEBUG: UDP Device Alive, Try Count:1, Time:1.7982 ms
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] DEBUG: Entering SNMP Ping
2018/01/05 12:50:32 - SPINE: Poller[1] Updating Full System Information Table
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] RECACHE: Processing 1 items in the auto reindex cache for '10.200.0.222'
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] Recache DataQuery[1] OID: .1.3.6.1.2.1.1.3.0, output: 98678200
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] NOTE: There are '21' Polling Items for this Device
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] DEBUG: The NIFTY POPEN returned the following File Descriptor 6
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[6281] SCRIPT: perl /var/www/html/cacti/scripts/ping.pl '10.200.0.222', output: 1.79
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10606] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305792, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10599] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304000, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10599] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304000, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10600] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304256, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10600] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304256, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10601] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304512, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10601] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304512, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10602] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194304768, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10602] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194304768, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10603] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305024, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10603] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305024, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10604] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305280, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10604] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305280, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10605] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305536, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10605] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305536, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10464] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.234946624, value: 571758503903
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10464] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.234946624, value: 21638631350677
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10463] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.234946560, value: 631266645
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10463] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.234946560, value: 242266413
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DS[10606] SNMP: v2: 10.200.0.222, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.4194305792, value: 18446744073709551615
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] Total Time: 0.16 Seconds
2018/01/05 12:50:32 - SPINE: Poller[1] Device[566] TH[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
2018/01/05 12:50:32 - SPINE: Poller[1] DEBUG: The Value of Active Threads is 0 for Device ID 566
SPINE: Time: 1.0320 s, Threads: 24, Devices: 1
Do You see this value: "18446744073709551615" its the same for all GPON ports so this is the purpose why this doesn't graph proper.
I tried to delete and add graphs. I tried to rebuild cache.
from spine.
Those are remarkably similar to 64bit unsigned overflow values. In other words, your counters are not properly overflowing, but rather getting stuck on overflow and need to be reset.
You need to contact your device vendor and ask them to fix the counters so that they either overflow or count down. Hopefully, the vendor gives you the option to reset them yourself in the mean time. This is why they don't graph.
As the original issue is fixed, I'll close this one out. Thanks for confirming.
from spine.
Ok - Do You know how to clear counters/statistics on Huawei MA5683T or change them to 64bit?
Cannot find this in documentation. Is flash erase the only one way?
from spine.
from the internet 'clear counters' is the command.
from spine.
Sorry 'reset counters interface'
from spine.
Doesn't work either.
:(
Whole time:
2018/01/05 20:07:32 - SPINE: Poller[1] Device[566] TH[1] DS[10605] SNMP: v2: 10.200.0.222, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.4194305536, value: 18446744073709551615
I am searching whole time ;)
from spine.
Open a ticket with Huawei.
from spine.
I get the same thing for almost all hosts. This appears to be a new problem.
from spine.
Related Issues (20)
- MySQL reconnect option is depreciated HOT 5
- Unix installation instructions missing call to ./bootstrap HOT 1
- Spine does not check a host with no poller items
- Cacti device status broken when the device does not have a graph. Cannot create graph for down device. HOT 21
- Poller may report the wrong number of devices polled HOT 5
- Can't compile spine on OpenBSD HOT 8
- Can't use spine, poller.php works HOT 15
- Allow users to override the threads setting at the command line HOT 1
- Reduce spine startup time by obtaining settings in bulk
- Allow spine to run in ping-only mode HOT 1
- Spine does not honor the number of threads defined in the cacti GUI HOT 7
- Fix Clang 16 compilation warnings under FreeBSD 14 HOT 3
- [1.3 QA] spine develop SQL Error with latest cacti develop HOT 6
- SPINE: Poller[Main Poller] PID[p id] PT[pt number] Device[Device Name] Hostname[IP Address] ERROR: HOST EVENT: Device is DOWN Message: ICMP: Ping timed out HOT 3
- Can't ping6 IPv6 hosts HOT 7
- AES192C / AES256C Cisco Privacy Protocol absent, net-snmp-1:5.9 - aka Cisco-AES-256 Privacy Type SNMPv3 HOT 7
- FATAL: Spine Encountered a Segmentation Fault HOT 2
- SPINE Poller reports the devices down, however, the devices are up HOT 3
- Removal of AES Privacy Protocol was pre-mature
- The Availability/Reachability setting of "Ping or SNMP Uptime" is not working in latest spine
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spine.