SPINE 1.2.24 - problems with unusual SNMP values?

[GGA]

Oh no, it seems I was a bit too hasty.
Even with the latest 1.2.x spine the are some unusable values. Strange thing, from the same device some values can be used and some can't.

A bulkget gives me all values I would expect:

Code: Select all

iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.1.1 = STRING: "000.6273 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.3.1 = STRING: "-002.2709 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.5.1 = STRING: "001.3232 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.7.1 = STRING: "000.6914 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.9.1 = STRING: "001.2962 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.10.1 = STRING: "-002.3792 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.257.1 = STRING: "001.2499 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.261.1 = STRING: "001.5155 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.3.263.1 = STRING: "002.1648 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.1.1 = STRING: "-007.6447 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.3.1 = STRING: "-002.8274 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.5.1 = STRING: "-020.4575 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.7.1 = STRING: "-012.3358 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.9.1 = STRING: "-006.8131 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.10.1 = STRING: "-007.8542 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.257.1 = STRING: "-007.8754 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.261.1 = STRING: "-019.7469 dBm Normal"
iso.3.6.1.4.1.1991.1.1.3.3.10.1.4.263.1 = STRING: "-011.0790 dBm Normal"

Now I spine where only the last two OIDs bring me a value.

Code: Select all

/usr/local/spine/bin/spine --first=80 --last=80 -R -S -V 5
...
Total[0.9604] Device[80] HT[1] DS[20833] TT[9.57] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.1.1, value: U
Total[0.9604] Device[80] HT[1] DS[20833] TT[9.58] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.1.1, value: U
Total[0.9604] Device[80] HT[1] DS[20834] TT[9.59] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.3.1, value: U
Total[0.9604] Device[80] HT[1] DS[20834] TT[9.61] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.3.1, value: U
Total[0.9604] Device[80] HT[1] DS[20835] TT[9.62] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.5.1, value: U
Total[0.9604] Device[80] HT[1] DS[20835] TT[9.63] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.5.1, value: U
Total[0.9660] Device[80] HT[1] DS[20836] TT[5.57] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.7.1, value: U
Total[0.9661] Device[80] HT[1] DS[20836] TT[5.64] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.7.1, value: U
Total[0.9661] Device[80] HT[1] DS[20837] TT[5.67] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.9.1, value: U
Total[0.9661] Device[80] HT[1] DS[20837] TT[5.70] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.9.1, value: U
Total[0.9662] Device[80] HT[1] DS[20838] TT[5.74] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.10.1, value: U
Total[0.9662] Device[80] HT[1] DS[20838] TT[5.77] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.10.1, value: U
Total[0.9662] Device[80] HT[1] DS[20839] TT[5.81] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.257.1, value: U
Total[0.9663] Device[80] HT[1] DS[20839] TT[5.84] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.257.1, value: U
Total[0.9663] Device[80] HT[1] DS[20840] TT[5.87] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.261.1, value: U
Total[0.9663] Device[80] HT[1] DS[20840] TT[5.89] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.261.1, value: U
Total[0.9712] Device[80] HT[1] DS[20841] TT[4.81] SNMP: v2: HOST, dsname: snIfMonitoringRxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.263.1, value: -010.8249
Total[0.9712] Device[80] HT[1] DS[20841] TT[4.87] SNMP: v2: HOST, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.263.1, value: 002.2190

I have no clue, other devices should draw two graphs and both are working. An other one has four and only three are there.
Any idea?

[Osiris]

Update the bug on GitHub. This is not the place to report this.

[TheWitness]

I had asked for some wireshark output.

[eduardomozart]

I will paste it to github.
The script is executable and it still works when I switch back to spine release 1.2.24:

latest 1.2.x branch

Code: Select all

Total[0.1978] The executable is '/usr/bin//var/www/cacti/scripts/bind-stats.sh' in '/var/www/cacti/scripts/bind-stats.sh 'HOST''
Total[0.1979] Device[3] ERROR: Problem executing POPEN.  File '/var/www/cacti/scripts/bind-stats.sh 'HOST'' does not exist or is not executable.

With spine release 1.2.24

Code: Select all

Total[0.2237] DEBUG: Device[3] DEBUG: The NIFTY POPEN returned the following File Descriptor 9
Total[0.2529] Device[3] HT[1] DS[595] TT[29.47] SCRIPT: /var/www/cacti/scripts/bind-stats.sh 'HOST', output: a:23726299 a6:1 aaaa:16733246 any:1572 cname:27042 mx:2257 naptr:42117 ns:5755 ptr:8034 soa:3460 spf:6 srv:934732 txt:19786 rsnx:749692 rsfail:76 rserr:7 rsipv4qs:1586174 rsipv4rr:1532849 rsmismatch: rsqr:1699338 rsqt:76206 rsrtt10:6476462 rsrtt100500:500206 rsrtt10100:2471797 rsrtt1600:577 rsrtt500800:4772 rsrtt8001600:979 sockopen:2435733 sockclosed:2435725 sockbf:189 consest:1584432 recverr:4364

I was having a similar problem on my Windows Cacti instance even on Spine 1.2.26 and I was able to fix it by running binaries on the following way:

CMD:

Code: Select all

C:/Spine/sh.exe -c "C:/Windows/System32/cmd.exe /c echo 30"

Bash:

Code: Select all

C:/Spine/sh.exe -c "echo 30"