group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #32261
[Bug 1843036] Re: [regression] SNMP missing disks in hrStorageTable
This bug was fixed in the package net-snmp - 5.7.3+dfsg-5ubuntu4
---------------
net-snmp (5.7.3+dfsg-5ubuntu4) eoan; urgency=medium
* d/p/put-paranthesis-around-macros-which-are-expressions.patch:
- put paranthesis around macros which are expressions.
(LP: #1843036)
-- Eric Desrochers <eric.desrochers@xxxxxxxxxxxxx> Fri, 06 Sep 2019
23:15:43 +0000
** Changed in: net-snmp (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1843036
Title:
[regression] SNMP missing disks in hrStorageTable
Status in net-snmp package in Ubuntu:
Fix Released
Status in net-snmp source package in Xenial:
In Progress
Status in net-snmp source package in Bionic:
In Progress
Status in net-snmp source package in Disco:
In Progress
Status in net-snmp source package in Eoan:
Fix Released
Bug description:
[IMPACT]
It has been brought to me the following:
Some hosts have started to cause UNKNOWN return values in Nagios for
checks on their disks. This is because these hosts are no longer
reporting their disks as part of the SNMP table hrStorageTable
(1.3.6.1.2.1.25.2.3.1 ) - only memory devices are being reported. The
affected hosts that I have investigated received updates for SNMP:
Upgrade package libsnmp-base 5.7.3+dfsg-1.8ubuntu3.1 to 5.7.3+dfsg-1.8ubuntu3.2
Upgrade package libsnmp30 5.7.3+dfsg-1.8ubuntu3.1 to 5.7.3+dfsg-1.8ubuntu3.2
Upgrade package snmpd 5.7.3+dfsg-1.8ubuntu3.1 to 5.7.3+dfsg-1.8ubuntu3.2
It seems likely that this package update is the cause.
As debug info, you can see the difference between 2 nearly identical
servers, one of which received the SNMP updates, and one which did
not. You can see that the one without the update is returning disks in
the SNMP output:
# snmpwalk -v2c -cpublic arcprsmt01 1.3.6.1.2.1.25.2.3.1.3
iso.3.6.1.2.1.25.2.3.1.3.1 = STRING: "Physical memory"
iso.3.6.1.2.1.25.2.3.1.3.3 = STRING: "Virtual memory"
iso.3.6.1.2.1.25.2.3.1.3.6 = STRING: "Memory buffers"
iso.3.6.1.2.1.25.2.3.1.3.7 = STRING: "Cached memory"
iso.3.6.1.2.1.25.2.3.1.3.8 = STRING: "Shared memory"
iso.3.6.1.2.1.25.2.3.1.3.10 = STRING: "Swap space"
iso.3.6.1.2.1.25.2.3.1.3.31 = STRING: "/"
iso.3.6.1.2.1.25.2.3.1.3.37 = STRING: "/run"
iso.3.6.1.2.1.25.2.3.1.3.39 = STRING: "/dev/shm"
iso.3.6.1.2.1.25.2.3.1.3.40 = STRING: "/run/lock"
iso.3.6.1.2.1.25.2.3.1.3.41 = STRING: "/sys/fs/cgroup"
iso.3.6.1.2.1.25.2.3.1.3.67 = STRING: "/run/snapd/ns"
iso.3.6.1.2.1.25.2.3.1.3.70 = STRING: "/var/lib/docker/containers/3cad3d36991b677c37b08b374a7bfeceddf36a6b6754edaa1ff687b00111a6b8/mounts/shm"
iso.3.6.1.2.1.25.2.3.1.3.73 = STRING: "/var/lib/docker/containers/c605c4b76dea65d562ba024212a38e24fb710186c499187b6604478b7ff678e9/mounts/shm"
iso.3.6.1.2.1.25.2.3.1.3.82 = STRING: "/run/user/2002"
iso.3.6.1.2.1.25.2.3.1.3.253 = STRING: "/var/lib/docker/containers/dc74a157fbaaa284e0e5b8ca4afc88769bf625eb796d89a5d26f98a540cabf35/mounts/shm"
iso.3.6.1.2.1.25.2.3.1.3.256 = STRING: "/var/lib/docker/containers/6ce6193433f9c1c95cccbfbbe08a3f3385bdbc4f2e3f0baa02d11baf3866dfd2/mounts/shm"
iso.3.6.1.2.1.25.2.3.1.3.258 = STRING: "/run/user/1000"
The other, which received SNMP updates, is returning only memory
devices, such as swap and shmem:
# snmpwalk -v2c -cpublic arcprsmt02 1.3.6.1.2.1.25.2.3.1.3
iso.3.6.1.2.1.25.2.3.1.3.1 = STRING: "Physical memory"
iso.3.6.1.2.1.25.2.3.1.3.3 = STRING: "Virtual memory"
iso.3.6.1.2.1.25.2.3.1.3.6 = STRING: "Memory buffers"
iso.3.6.1.2.1.25.2.3.1.3.7 = STRING: "Cached memory"
iso.3.6.1.2.1.25.2.3.1.3.8 = STRING: "Shared memory"
iso.3.6.1.2.1.25.2.3.1.3.10 = STRING: "Swap space"
[Test Case]
* Install snmp snmpd
* Configure /etc/snmp/snmpd.conf by adding the following:
view systemonly included .1.3.6.1.2.1.25.2.3.1.3
* Restart snmpd
* Use snmpwalk:
** snmpwalk -v2c -cpublic localhost 1.3.6.1.2.1.25.2.3.1.3
Expected behavior is to see the disk as follow:
"
iso.3.6.1.2.1.25.2.3.1.3.1 = STRING: "Physical memory"
iso.3.6.1.2.1.25.2.3.1.3.3 = STRING: "Virtual memory"
iso.3.6.1.2.1.25.2.3.1.3.6 = STRING: "Memory buffers"
iso.3.6.1.2.1.25.2.3.1.3.7 = STRING: "Cached memory"
iso.3.6.1.2.1.25.2.3.1.3.8 = STRING: "Shared memory"
iso.3.6.1.2.1.25.2.3.1.3.10 = STRING: "Swap space"
iso.3.6.1.2.1.25.2.3.1.3.31 = STRING: "/"
iso.3.6.1.2.1.25.2.3.1.3.33 = STRING: "/dev"
iso.3.6.1.2.1.25.2.3.1.3.45 = STRING: "/dev/lxd"
iso.3.6.1.2.1.25.2.3.1.3.46 = STRING: "/dev/.lxd-mounts"
iso.3.6.1.2.1.25.2.3.1.3.63 = STRING: "/proc/sys/kernel/random/boot_id"
iso.3.6.1.2.1.25.2.3.1.3.66 = STRING: "/dev/shm"
iso.3.6.1.2.1.25.2.3.1.3.67 = STRING: "/run"
iso.3.6.1.2.1.25.2.3.1.3.68 = STRING: "/run/lock"
iso.3.6.1.2.1.25.2.3.1.3.69 = STRING: "/sys/fs/cgroup"
"
[Potential Regression]
The fix has been tested by various impacted users, and feedback were all positives. Note that this fix a regression introduced by: https://bugs.launchpad.net/bugs/1835818
[Other information]
# Upstream commit:
https://github.com/net-snmp/net-snmp/commit/71e487212bd65839e7454df9701524d08cf0d74f
# git describe --contains 71e487212bd65839e7454df9701524d08cf0d74f
v5.8.pre1
# rmadison:
net-snmp | 5.7.3+dfsg-1ubuntu4 | xenial | source
net-snmp | 5.7.3+dfsg-1ubuntu4.2 | xenial-security | source
net-snmp | 5.7.3+dfsg-1ubuntu4.2 | xenial-updates | source
net-snmp | 5.7.3+dfsg-1ubuntu4.3 | xenial-proposed | source
net-snmp | 5.7.3+dfsg-1.8ubuntu3 | bionic | source
net-snmp | 5.7.3+dfsg-1.8ubuntu3.1 | bionic-security | source
net-snmp | 5.7.3+dfsg-1.8ubuntu3.1 | bionic-updates | source
net-snmp | 5.7.3+dfsg-1.8ubuntu3.2 | bionic-proposed | source
net-snmp | 5.7.3+dfsg-5ubuntu1 | disco | source
net-snmp | 5.7.3+dfsg-5ubuntu1.1 | disco-proposed | source
net-snmp | 5.7.3+dfsg-5ubuntu3 | eoan | source
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036/+subscriptions