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.

Description of problem:
 The reposd process fails with a SIGFPE with the following signature:

(gdb) bt
#0  metricCalcPageOutRate (mv=0x96b877f0, mnum=<value optimized out>, v=0x96b8f3e8, vlen=<value optimized out>) at /usr/include/bits/string3.h:52
#1  0x0000004b6e6a33f4 in reposvalue_get (vs=0x96b75e58, ch=0x96b65820) at repos.c:385
#2  0x0000000080002732 in main (argc=<value optimized out>, argv=<value optimized out>) at reposd.c:474


Version-Release number of selected component (if applicable):
 sblim-gather-2.2.3-3.el6

How reproducible:
 Difficult, only observed in end customer deployment

Steps to Reproduce:
1. Deploy and configure sblim-gather SFCB
2. Monitor for reposd to encounter a SIGFPE
3.

Actual results:
 reposd encounters the SIGFPE and fails

Expected results:
 reposd continues executing

Additional info:
 Believed to be an instance of the upstream issue below:

    Standards Based Linux Instrumentation / Bugs / #2739 gatherer reposd SIGFPE during calculation of interval metric
    https://sourceforge.net/p/sblim/bugs/2739/

Created attachment 1235518 [details]
Backport of upstream adb18fc7 - "Fixed #2739: reposd SIGFPE during calculation of interval metric"

Patch to avoid the resulting SIGFPE when duplicate entries are present. Backported from upstream commit:

commit adb18fc7b8eaa97c731d947d9773721e58dc8d9c
Author: Dave Heller <hellerda.com>
Date:   Mon Oct 6 01:39:14 2014 -0400

    Fixed #2739: reposd SIGFPE during calculation of interval metric

Applies cleanly to sblim-gather-2.2.3-3.el6.

Test build:
  https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12279349

- Kyle Walker

Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
 
The official life cycle policy can be reviewed here:
 
http://redhat.com/rhel/lifecycle
 
This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
 
https://access.redhat.com