Description of problem:
After upgrading to net-snmp-5.5-49.el6_5.2, hrSystemProcesses is no longer available:
# snmpwalk -c public -v 2c 127.0.0.1 | grep hrSystemProcesses
HOST-RESOURCES-MIB::hrSWRunParameters.30137 = STRING: "--color=auto hrSystemProcesses"
# snmpwalk -c public -v 2c -On 127.0.0.1 | grep ".22.214.171.124.126.96.36.199.6."
.188.8.131.52.184.108.40.206.220.127.116.11247 = STRING: "--color=auto .18.104.22.168.22.214.171.124.6."
Version-Release number of selected component (if applicable):
Thanks for the bug report. hrSystemProcesses has slipped through cracks in our process.
Upstream patch: 680011dcaf92ac67f6a1e77826b83a382d415a42
Sigh, upstream patch: https://sourceforge.net/p/net-snmp/code/ci/7ce46bd526e340ddf328d68fa6de1b6f204b8294/
Commit 680011dcaf92ac67f6a1e77826b83a382d415a42 fix the problem with hrSystemProcesses. Thank you.
Hit by this bug, too, when can be expected to get an updated version? This issue causes huge problems in process monitoring via Nagios and we had to downgrade.
Note that Bugzilla is not a support tool. Please contact your Red Hat support at access.redhat.com to get the service you pay for.
[In other words: please open a ticket there. Complaining in Bugzilla and/or raising bug priority won't speed things up in any way.]
Ticket 01183465 created
*** Bug 1139485 has been marked as a duplicate of this bug. ***
Exactly WHY did you make this bug private? Is this kind of joke or something? rhel is not going to be more secure if you HIDE bugs. On the other hand, testing will. But seeing a lot of crappy updates lately and rhel7 (gnome,systemd/etc.) seems like testing is not one of redhat priorities.
Please remove the private flag. If not, fell free to remove Reporter and CC List flags for me. I don't f*** care.
I also fail to see how making the bug private helps in addressing the issue.
Please, use private comments in case you need to attach a private message.
I'm very sorry I didn't check that the reporter is an external user.
In that case, I should not have changed the flag.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.