Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
The previous Net-SNMP update contained a fix to improve checking of invalid incoming SNMP messages. This fix introduced a regression and some valid SNMP messages with multiple variables inside might be marked as invalid.
Consequence:
Net-SNMP tools and servers might reject valid SNMP messages and wait for "proper" response until timeout.
Fix:
Valid SNMP messages are not rejected.
Result:
The servers and utilities accept first incoming message and do not wait for a timeout.
Description of problem:
after update from net-snmp 1:5.5-44.el6_4.1 to 1:5.5-44.el6_4.2
a snmp query times out
Version-Release number of selected component (if applicable): 1:5.5-44.el6_4.1/1:5.5-44.el6_4.2
How reproducible:
Steps to Reproduce:
1. yum rollback
2. test
3. yum install, test again
Actual results:
$ time { snmpbulkwalk -t 30 -v2c -c 'xxxxx' -m '' -M '' -Cc -On -Ob -OQ -Ot 145.92.231.151 1.3.6.1.4.1; }
.1.3.6.1.4.1.2021.2.1.1.1 = 1
[cut]
Timeout: No Response from 145.92.231.151
real 3m0.275s
user 0m0.002s
sys 0m0.003s
Expected results:
$ time { snmpbulkwalk -t 30 -v2c -c 'xxxxx' -m '' -M '' -Cc -On -Ob -OQ -Ot 145.92.231.151 1.3.6.1.4.1; }
.1.3.6.1.4.1.2021.2.1.1.1 = 1
[cut]
.1.3.6.1.4.1.8072.1.3.2.1.0 = 0
real 0m20.090s
user 0m0.488s
sys 0m0.187s
real 0m20.090s
user 0m0.488s
sys 0m0.187s
Additional info:
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.
http://rhn.redhat.com/errata/RHBA-2013-1693.html
Description of problem: after update from net-snmp 1:5.5-44.el6_4.1 to 1:5.5-44.el6_4.2 a snmp query times out Version-Release number of selected component (if applicable): 1:5.5-44.el6_4.1/1:5.5-44.el6_4.2 How reproducible: Steps to Reproduce: 1. yum rollback 2. test 3. yum install, test again Actual results: $ time { snmpbulkwalk -t 30 -v2c -c 'xxxxx' -m '' -M '' -Cc -On -Ob -OQ -Ot 145.92.231.151 1.3.6.1.4.1; } .1.3.6.1.4.1.2021.2.1.1.1 = 1 [cut] Timeout: No Response from 145.92.231.151 real 3m0.275s user 0m0.002s sys 0m0.003s Expected results: $ time { snmpbulkwalk -t 30 -v2c -c 'xxxxx' -m '' -M '' -Cc -On -Ob -OQ -Ot 145.92.231.151 1.3.6.1.4.1; } .1.3.6.1.4.1.2021.2.1.1.1 = 1 [cut] .1.3.6.1.4.1.8072.1.3.2.1.0 = 0 real 0m20.090s user 0m0.488s sys 0m0.187s real 0m20.090s user 0m0.488s sys 0m0.187s Additional info: