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.
Previously, snmptrapd daemon destroyed embedded perl interpreter immediately when TERM signal was received, regardless if the embedded perl was still used or not. This could lead to rare crashes of the daemon during shutdown.
In this update, the embedded perl interpreter is destroyed later during the daemon shutdown, when all perl processing is already finished.
snmptrapd destroys embeded perl in TERM signal handler. After snmptrapd handles the signal, it returns to processing of incoming traps and if embedded perl is enabled, it may call it. But the embedded perl is already destroyed -> SIGSEGV.
This bug is reproducible only with valgrind-3.6.0-5.el6, older -4.el6 release does not exhibit this bug.
(In reply to comment #0)
> How reproducible:
> always
I would say it's reproducible in about 30% of test runs on my virtual machine, definitely not 100%.
Comment 4RHEL Program Management
2012-09-10 08:19:36 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
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-0421.html
Created attachment 586321 [details] valgrind log Description of problem: snmptrapd core dumps while running within valgrind with perl trap handler. # cat /etc/snmp/snmptrapd.conf disableAuthorization yes perl do "/usr/local/bin/trapreciver.pl"; # cat /usr/local/bin/trapreciver.pl #!/usr/bin/perl use SNMP; sub my_receiver { print "Trap received\n"; } NetSNMP::TrapReceiver::register("all", \&my_receiver) or warn "Failed to register Perl trap handler\n"; print "Registered Perl trap handler\n"; Version-Release number of selected component (if applicable): net-snmp-5.5-41.el6 valgrind >= 3.6.0-5.el6 How reproducible: always Steps to Reproduce: 1. # valgrind -v --leak-check=yes /usr/sbin/snmptrapd -Lsd -p /var/run/snmptrapd.pid -f & 2. send trap: # service restart snmpd 3. kill %1 Actual results: snmptrapd core dumps Expected results: no core dump Additional info: