Bug 736264
Summary: | snmpd: error finding row index in _ifXTable_container_row_restore | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Josef Möllers <josef.moellers> | ||||
Component: | net-snmp | Assignee: | Jan Safranek <jsafrane> | ||||
Status: | CLOSED ERRATA | QA Contact: | Dalibor Pospíšil <dapospis> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 5.7 | CC: | dapospis, gasmith, ksrot, ovasik, rdassen, ykinoshi | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | SA233413396 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Prior to this update, snmpd reported 'snmpd: error finding row index in _ifXTable_container_row_restore' in system log when the snmpd was started and did not find a network interface, which was present during last snmpd shutdown. This happened usually on systems, which dynamically create and remove network interfaces on demand, like virtual hosts or PPP servers. In this update, this message was removed and it should not appear in system log.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 788954 (view as bug list) | Environment: | |||||
Last Closed: | 2012-02-21 06:32:17 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 788954 | ||||||
Attachments: |
|
Description
Josef Möllers
2011-09-07 08:27:22 UTC
The message is completely harmless. snmpd stores table of network interfaces on shutdown and tries to restore it on next start. The message is shown if the set of interfaces is different on shutdown and the next start, typically when an interface is removed. I'll try to lower severity of the message so it's shown only when debug logs are explicitly requested. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Prior to this update, snmpd reported 'snmpd: error finding row index in _ifXTable_container_row_restore' in system log when the snmpd was started and did not find a network interface, which was present during last snmpd shutdown. This happened usually on systems, which dynamically create and remove network interfaces on demand, like virtual hosts or PPP servers. In this update, severity of this message is lowered and it should not appear in system log. (In reply to comment #1) > I'll try to lower severity of the message so it's shown only when debug logs > are explicitly requested. I removed the message completely, it's quite useless. Sorry for the confusion. Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Prior to this update, snmpd reported 'snmpd: error finding row index in _ifXTable_container_row_restore' in system log when the snmpd was started and did not find a network interface, which was present during last snmpd shutdown. This happened usually on systems, which dynamically create and remove network interfaces on demand, like virtual hosts or PPP servers. In this update, severity of this message is lowered and it should not appear in system log.+Prior to this update, snmpd reported 'snmpd: error finding row index in _ifXTable_container_row_restore' in system log when the snmpd was started and did not find a network interface, which was present during last snmpd shutdown. This happened usually on systems, which dynamically create and remove network interfaces on demand, like virtual hosts or PPP servers. In this update, this message was removed and it should not appear in system log. 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-2012-0165.html |