Hi Adam,
Thanks, we have indeed confirmed that rolling back that package fixes it (as does upgrading it to 3.3) - will wait and see how long for it to get pushed out now. Cheers!
Robert Williams Custodian Data Centres https://www.CustodianDC.com From: observium observium-bounces@observium.org On Behalf Of Adam Armstrong via observium Sent: 09 September 2019 12:16 To: 'Observium' observium@observium.org Cc: adama@memetic.org Subject: Re: [Observium] Ubuntu Storage
WARNING: This email may contain attachments that have bypassed our filters. Please be cautious. If in doubt, speak to the NOC first. You can ignore this warning if there aren't any visible attachments.
________________________________
Apparently this is a regression that they're in the process of fixing. It was accepted into bionic-proposed a few hours ago.
You can probably use these packages to fix it :
https://launchpad.net/ubuntu/+source/net-snmp/5.7.3+dfsg-1.8ubuntu3.3/+build...
Adam.
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Robert Williams via observium Sent: 09 September 2019 10:12 To: 'Observium' <observium@observium.orgmailto:observium@observium.org> Cc: Robert Williams <Robert@CustodianDC.commailto:Robert@CustodianDC.com> Subject: [Observium] Ubuntu Storage
Hi,
Only just started looking into this, but it seems that all Ubuntu 18.04 hosts which auto-update have pulled snmpd up to 5.7.3+dfsg-1.8ubuntu3.2 (from ubuntu3.1) are now no longer providing 'any' of their storage info under hrStorageEntry
# /usr/bin/snmpbulkwalk -t '5' -r '3' -v2c -c *** -Pud -OQUs -m HOST-RESOURCES-MIB:HOST-RESOURCES-TYPES -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'target-device':'161' hrStorageEntry
hrStorageEntry = No Such Object available on this agent at this OID
But - after a restart of SNMPD service on the target-device, the expected response returns correctly:
hrStorageIndex.1 = 1 hrStorageIndex.3 = 3 hrStorageIndex.6 = 6 hrStorageIndex.7 = 7 hrStorageIndex.8 = 8 hrStorageIndex.10 = 10 hrStorageType.1 = hrStorageRam hrStorageType.3 = hrStorageVirtualMemory hrStorageType.6 = hrStorageOther hrStorageType.7 = hrStorageOther hrStorageType.8 = hrStorageOther <...>
HOWEVER - a re-discovery and poll of the device by Observium kills it immediately, and it goes back to:
hrStorageEntry = No Such Object available on this agent at this OID
It has impacted every 18.04 device we have which auto-updates.
Anyone else seen this?
Robert Williams Custodian Data Centres https://www.CustodianDC.com