- observium - lists.observium.org

Storage and Temperatures/Voltages/Fans gone missing
by Niklas Larsson 07 Oct '13

07 Oct '13

Hi, after som updates (now on the latest public SVN) I have lost temperatures on my SuperMicro boxes. And on some the storage as well. Log from ./discovery.php -d -h box01.example.com: https://gist.github.com/pnlarsson/2d207c05a47cc4de1361 Temperatures/Voltages/Fans: They all went to 0 around 2013-07-10 (Voltage -12V above threshold: 0 V (> -10.729 V)). And deleted 2013-08-25 (Sensor Deleted: voltage supermicro 9 CPU1 Vcore). I can get the temperatures/voltage/fans from cli with sd2 and from smtp with: [root@observium observium]# snmpwalk -v2c -c 'SuperDuperPassword' box01.example.com .1.3.6.1.4.1.10876 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.1 = STRING: "Fan1 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.2 = STRING: "Fan2 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.3 = STRING: "Fan3 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.4 = STRING: "Fan4 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.5 = STRING: "Fan5 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.6 = STRING: "Fan6 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.7 = STRING: "Fan7 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.8 = STRING: "Fan8 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.9 = STRING: "CPU1 Vcore Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.10 = STRING: "CPU2 Vcore Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.11 = STRING: "CPU1 DIMM Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.12 = STRING: "CPU2 DIMM Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.13 = STRING: "+5V Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.14 = STRING: "+5VSB Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.15 = STRING: "+12V Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.16 = STRING: "-12V Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.17 = STRING: "+3.3V Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.18 = STRING: "+3.3Vsb Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.19 = STRING: "VBAT Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.20 = STRING: "CPU1 Temperature" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.21 = STRING: "CPU2 Temperature" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.22 = STRING: "System Temperature" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.23 = STRING: "Chassis Intrusion" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.24 = STRING: "Power Supply Failure" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.25 = STRING: "DIMM Temperature" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.1 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.2 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.3 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.4 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.5 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.6 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.7 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.8 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.9 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.10 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.11 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.12 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.13 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.14 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.15 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.16 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.17 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.18 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.19 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.20 = INTEGER: 2 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.21 = INTEGER: 2 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.22 = INTEGER: 2 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.23 = INTEGER: 3 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.24 = INTEGER: 3 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.25 = INTEGER: 3 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.1 = INTEGER: 8437 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.2 = INTEGER: 8437 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.3 = INTEGER: 8437 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.4 = INTEGER: 8437 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.5 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.6 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.7 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.8 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.9 = INTEGER: 1072 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.10 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.11 = INTEGER: 1368 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.12 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.13 = INTEGER: 5120 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.14 = INTEGER: 5120 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.15 = INTEGER: 12286 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.16 = INTEGER: -11891 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.17 = INTEGER: 3264 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.18 = INTEGER: 3288 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.19 = INTEGER: 3216 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.20 = INTEGER: 27 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.21 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.22 = INTEGER: 19 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.23 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.24 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.4.25 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.9 = INTEGER: 1488 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.10 = INTEGER: 1488 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.11 = INTEGER: 1648 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.12 = INTEGER: 1648 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.13 = INTEGER: 5504 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.14 = INTEGER: 5504 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.15 = INTEGER: 13187 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.16 = INTEGER: -10729 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.17 = INTEGER: 3648 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.18 = INTEGER: 3648 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.19 = INTEGER: 3648 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.20 = INTEGER: 95 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.21 = INTEGER: 95 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.5.22 = INTEGER: 75 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.1 = INTEGER: 715 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.2 = INTEGER: 715 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.3 = INTEGER: 715 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.4 = INTEGER: 715 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.5 = INTEGER: 715 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.6 = INTEGER: 715 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.7 = INTEGER: 715 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.8 = INTEGER: 715 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.9 = INTEGER: 600 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.10 = INTEGER: 600 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.11 = INTEGER: 1352 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.12 = INTEGER: 1352 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.13 = INTEGER: 4512 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.14 = INTEGER: 4512 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.15 = INTEGER: 10803 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.16 = INTEGER: -13246 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.17 = INTEGER: 2952 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.18 = INTEGER: 2952 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.6.19 = INTEGER: 2952 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.1 = INTEGER: 84375 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.2 = INTEGER: 84375 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.3 = INTEGER: 84375 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.4 = INTEGER: 84375 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.5 = INTEGER: 84375 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.6 = INTEGER: 84375 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.7 = INTEGER: 84375 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.8 = INTEGER: 84375 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.9 = INTEGER: 2040 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.10 = INTEGER: 2040 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.11 = INTEGER: 2040 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.12 = INTEGER: 2040 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.13 = INTEGER: 8160 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.14 = INTEGER: 8160 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.15 = INTEGER: 13504 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.16 = INTEGER: 1854 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.17 = INTEGER: 6120 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.18 = INTEGER: 6120 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.19 = INTEGER: 6120 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.20 = INTEGER: 127 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.21 = INTEGER: 127 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.22 = INTEGER: 127 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.23 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.24 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.7.25 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.1 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.2 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.3 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.4 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.5 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.6 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.7 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.8 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.9 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.10 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.11 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.12 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.13 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.14 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.15 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.16 = INTEGER: -47513 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.17 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.18 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.19 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.20 = INTEGER: 4294967169 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.21 = INTEGER: 4294967169 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.22 = INTEGER: 4294967169 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.23 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.24 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.8.25 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.9.1 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.9.2 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.9.3 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.9.4 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.9.5 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.9.6 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.9.7 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.9.8 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.1 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.2 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.3 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.4 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.5 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.6 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.7 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.8 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.9 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.10 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.11 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.12 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.13 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.14 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.15 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.16 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.17 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.18 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.19 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.20 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.21 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.22 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.23 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.24 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.10.25 = INTEGER: 1 but if fails after a while with snmpbulkwalk: [root@observium observium]# snmpbulkwalk -v2c -c 'SuperDuperPassword' box01.example.com .1.3.6.1.4.1.10876 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.1 = STRING: "Fan1 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.2 = STRING: "Fan2 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.3 = STRING: "Fan3 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.4 = STRING: "Fan4 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.5 = STRING: "Fan5 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.6 = STRING: "Fan6 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.7 = STRING: "Fan7 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.8 = STRING: "Fan8 Fan Speed" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.9 = STRING: "CPU1 Vcore Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.10 = STRING: "CPU2 Vcore Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.11 = STRING: "CPU1 DIMM Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.12 = STRING: "CPU2 DIMM Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.13 = STRING: "+5V Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.14 = STRING: "+5VSB Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.15 = STRING: "+12V Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.16 = STRING: "-12V Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.17 = STRING: "+3.3V Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.18 = STRING: "+3.3Vsb Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.19 = STRING: "VBAT Voltage" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.20 = STRING: "CPU1 Temperature" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.21 = STRING: "CPU2 Temperature" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.22 = STRING: "System Temperature" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.23 = STRING: "Chassis Intrusion" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.24 = STRING: "Power Supply Failure" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.2.25 = STRING: "DIMM Temperature" SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.1 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.2 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.3 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.4 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.5 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.6 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.7 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.8 = INTEGER: 0 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.9 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.10 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.11 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.12 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.13 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.14 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.15 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.16 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.17 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.18 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.19 = INTEGER: 1 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.20 = INTEGER: 2 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.21 = INTEGER: 2 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.22 = INTEGER: 2 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.23 = INTEGER: 3 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.24 = INTEGER: 3 SNMPv2-SMI::enterprises.10876.2.1.1.1.1.3.25 = INTEGER: 3 Timeout: No Response from box01.example.com Storage: SNMP is returning storage and I'm using the linux/unix agent as well and it's echoing: <<<df>>> /dev/md0 ext4 468688256 3227188 441653076 1% / <<<mounts>>> /dev/md0 / ext4 rw,relatime,barrier=1,data=ordered 0 0 but the graphs are not there any more. Can't find anything in the event logs either concerning storage. /niklas

4 6

Ramsay in da haus!
by Rob VanHooren 07 Oct '13

07 Oct '13

aye, the Gordon Ramsay of network monitoring. :-D (f**king donkey… ) On 2013-10-07, at 7:00 AM, observium-request(a)observium.org wrote: > But hey, if this is the bullshit we get for continuing to release an > Open Source version, maybe we'll stop doing that...

1 0

login page: mention observium or not?
by Adam Armstrong 07 Oct '13

07 Oct '13

Hi Guys, Straw poll: Should we mention Observium on the login page or not? I've historically avoided it because dumb security auditors are easily placated by security through obscurity. adam.

2 1

Re: [Observium] Observium Community / Professional
by Adam Armstrong 06 Oct '13

06 Oct '13

Win... Rar... I don't even. Leslie-Alexandre DENIS <infoslad(a)gmail.com> wrote: >As for me the tar.gz provided at >http://www.observium.org/observium-community-latest.tar.gz is corrupted >(opened with WinRAR). Don't think it's on me, just saying. > >Regards >Le 06/10/2013 17:55, Adam Armstrong a écrit : >> They were already on the Ubuntu/Debian guide, I've added them to the >> RHEL/Centos/etc guide. >> >> I think there is some scope for merging the guides, actually... >> >> adam. >> >> >> On 2013-10-06 16:39, Jared Beaulieu wrote: >>> Does the install page need to be updated with a link to the tar file >>> for the Open Source edition? >>> >>> - Jared >>> >>> ------------------------- >>> FROM: Adam Armstrong <adama(a)memetic.org> >>> TO: observium(a)observium.org >>> SENT: Friday, October 4, 2013 11:48 AM >>> SUBJECT: [Observium] Observium Community / Professional >>> >>> Hi Guys, >>> >>> As we talked about in April, to sustain development we need to develop a >>> revenue stream. >>> >>> The temporary solution in April was the Kickstarter, which funded 6 >>> months of development for the alerting system. To fund development after >>> that, we've decided to try a relatively inexpensive subscription scheme. >>> >>> http://www.observium.org/Edition_Split [1] >>> >>> The intention is to provide enough for free to keep the people who >>> wouldn't ever pay happy, and try to keep the price low enough that >>> everyone else can pay without worrying too much about it. >>> >>> We've set the subscription at £100/year. If you were a Kickstarter >>> supporter, you'll get a free subscription for a while, because we're >>> nice like that. >>> >>> Comments? :) >>> >>> adam. >>> _______________________________________________ >>> observium mailing list >>> observium(a)observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2] >>> >>> >>> >>> Links: >>> ------ >>> [1] http://www.observium.org/Edition_Split >>> [2] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >>> >>> _______________________________________________ >>> observium mailing list >>> observium(a)observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >> _______________________________________________ >> observium mailing list >> observium(a)observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

sign up for pro service
by Zach Underwood 06 Oct '13

06 Oct '13

I am backer of $100 on kickstarter, how do I get a log on for the pro version of svn. -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website <http://zachunderwood.me> My photos <http://zunder1990.openphoto.me>

3 4

boo! re: mkpasswd
by Rob VanHooren 06 Oct '13

06 Oct '13

boo! md5 is deprecated. (read: cracked) http://tools.ietf.org/html/rfc6151 sha1 is likely to suffer the same fate. able to use at least sha256 ? R. On 2013-10-06, at 7:00 AM, observium-request(a)observium.org wrote: > Send me a password hash from 'mkpasswd -5' and a username and I'll add > you to the user list. > > Thanks, > adam.

2 1

Re: [Observium] Observium Community / Professional
by Gerwin Krist 05 Oct '13

05 Oct '13

Hi, I understand the change. And personally I think the price is oke, but I don't hope it will sky-rocket in the near feature. For us the MOST important thing is the Alerting (eg. IF up/down) part. But right now it's very limited and not working very well for us. Make it more less-complicated would be nice :-D When we can use it as reliable monitoring platform too, we are in! One other part: also support RHEL/CENTOS. It's an widely used enterprise OS and can't be ignored imho. - Gerwin

1 0

No Auth - adding new graph_type
by Micah Young 04 Oct '13

04 Oct '13

Hi, So I'm adding a new graph type and new sub-type but even as an administrator, it shows up as the pinked out No-Auth image. Did I miss a step? Mike Y. ________________________________ ARDEN A Global Company Celebrating over 48 years of making your life more comfortable! This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. This OUTBOUND E-mail and Document(s) has been scanned by an Antivirus Server.

1 0

Bug in SLA addition?
by Eric Stewart 04 Oct '13

04 Oct '13

Putting together a test box on CentOS 6.4 today to get a feel for it. If it works for us (though there are some hurdles), we'll look at it as a long term replacement to our largely homegrown MRTG installation. One of the many things I was happy to find that Observium is doing out of the box is Cisco IP SLA graphing. However, I'm running into an issue. The rrds are not being created and the graphs are empty. I set up config.php to enable_sla, and taking a clue from something I came across in the archives, I ran: ./poller.php -d -h <hostname> In the debug, a couple of things show up: SLA 121: jitter IP SLA SVC to Villages Low Priority... RRD[/usr/bin/rrdtool create /usr/local/apps/observium/rrd/<hostname>/sla-121.rrd \ DS:rtt:GAUGE:600:0:300000 --step 300 RRA:AVERAGE:0.5:1:2016 RRA:AVERAGE:0.5:6:2976 RRA:AVERAGE:0.5:24:1440 RRA:AVERAGE:0.5:288:1440 RRA:MIN:0.5:6:1440 RRA:MIN:0.5:96:360 RRA:MIN:0.5:288:1440 RRA:MAX:0.5:6:1440 RRA:MAX:0.5:96:360 RRA:MAX:0.5:288:1440 ] ERROR: can't parse argument ' DS:rtt:GAUGE:600:0:300000' 17ms at 2013-10-03 11:11:59RRD[cmd[update /usr/local/apps/observium/rrd/<hostname>/sla-121.rrd 1380813119:17] stdout[ERROR: opening '/usr/local/apps/observium/rrd/<hostname>/sla-121.rrd': No such file or directory] stderr[]] SLA 130: jitter IP SLA SVC to Mote High Priority... RRD[/usr/bin/rrdtool create /usr/local/apps/observium/rrd/<hostname>/sla-130.rrd \ DS:rtt:GAUGE:600:0:300000 --step 300 RRA:AVERAGE:0.5:1:2016 RRA:AVERAGE:0.5:6:2976 RRA:AVERAGE:0.5:24:1440 RRA:AVERAGE:0.5:288:1440 RRA:MIN:0.5:6:1440 RRA:MIN:0.5:96:360 RRA:MIN:0.5:288:1440 RRA:MAX:0.5:6:1440 RRA:MAX:0.5:96:360 RRA:MAX:0.5:288:1440 ] ERROR: can't parse argument ' DS:rtt:GAUGE:600:0:300000' 10ms at 2013-10-03 11:12:03RRD[cmd[update /usr/local/apps/observium/rrd/<hostname>/sla-130.rrd 1380813123:10] stdout[ERROR: opening '/usr/local/apps/observium/rrd/<hostname>/sla-130.rrd': No such file or directory] stderr[]] So obviously there's an "ERROR" there about parsing one of the arguments fed to the file creation. Any ideas? -- Eric Stewart - Network Administrator - eric(a)usf.edu University of South Florida, Information Technology

3 5

Running observium on multiple hosts
by Eric Stewart 03 Oct '13

03 Oct '13

I'm looking for some feedback/ideas on how others may have implemented Observium in a multi-site capacity. We are currently using MRTG to provide our data collection and graphing. While Observium isn't a perfect replacement for us, it goes a long way towards replacing much of what MRTG does. Our current setup involves a large university campus. We have core, distribution, and access layers, and at the distribution layers we've implemented monitoring systems for packet capture and (you guessed it) MRTG. This allows for: - Data collection to continue even if a distribution layer site is isolated from the core - Prevents data collection bandwidth from impacting the core Our MRTG data presentation is largely homegrown, and how we go about it isn't important. What I'm looking for are suggestions on how one might take a multi-server setup and allow someone to search or navigate to a given building or switch without having to guess as to which distribution site it's out of. Ideas rattling around my head right now involve: - Coding up the search function so that it not only searches the local site, but also all of the other servers - Coming up with some static page that indicates that a given building is off of a given installation - this one I don't like so much So I'm wondering if this is something someone else has put time and effort into and has a viable solution. -- Eric Stewart - Network Administrator - eric(a)usf.edu University of South Florida, Information Technology

1 0