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.

+++ This bug was initially created as a clone of Bug #888271 +++

Investigation of [bug 847289] showed snmpd is not careful about dynamic
modules when it comes to reloading the configuration (such as upon
receiving SIGHUP).

Dynamic modules seems to be loaded anew, which may corrupt previous
instances, avoid a proper cleanup actions and the like.
As per Jan Safranek, there is a room for improvement and less
error-prone behavior.

--- Additional comment from Jan Safranek on 2012-12-18 07:32:15 EST ---

snmpd should not call init_<modulename> when the module is already loaded.

This implies that snmpd never reloads modules and the only way to update a module is to restart snmpd.

Sorry for the noise, I came to the conclusion the current behavior is
OK and the limitation + solution are known [1].

Unless there is another issue with the current state, I would prefer
it as a status quo (maybe a sanity check at other dynamic modules we
provide should be performed -- generally, unregister registered MIBs
and registered alarms in deinit_<module> function).

[1] http://www.net-snmp.org/wiki/index.php/TUT:Writing_a_Dynamically_Loadable_Object#Initialization