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.

Bug 1848995

Summary:

Intermittent pminfo crashes (core dumps)

Product:

Red Hat Enterprise Linux 8

Reporter:

Jan Kurik <jkurik>

Component:

pcp

Assignee:

Nathan Scott <nathans>

Status:

CLOSED ERRATA

QA Contact:

Jan Kurik <jkurik>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

8.3

CC:

agerstmayr, jkurik, mgoodwin, nathans, patrickm

Target Milestone:

Keywords:

Bugfix, Triaged

Target Release:

8.3

Flags:

pm-rhel: mirror+

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

pcp-5.1.1-3

Doc Type:

No Doc Update

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2020-11-04 03:00:37 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
ABRT report of a pminfo crash	none

Description Jan Kurik 2020-06-19 12:51:18 UTC

Created attachment 1698083 [details]
ABRT report of a pminfo crash

Description of problem:
This is something I can not reliably reproduce, however from time to time pminfo crashes (SIGSEGV) dumping a core file. Typically this happens during run of test-case #688 of the pcp-testsuite.

Version-Release number of selected component (if applicable):
pcp-5.1.1-1.el8 and pcp-5.1.1-2.el8

How reproducible:
Intermittently

Steps to Reproduce:
1. Install pcp-testsuite
# yum install - pcp-testsuite
2. Run testcase #688
# cd /var/lib/pcp/testsuite && ./check 688

Actual results:
Sometimes the test-case #688 fails with an output similar to this:

> ./688: line 57: 836475 Segmentation fault      (core dumped) pminfo -d -Dderive,appl0 qa > $tmp.out 2>&1
94,136c95
< expr node <addr-24> type=FILTERINST left=<addr-25> right=<addr-26> save_last=0
< expr node <addr-25> type=PATTERN pattern: \[1\]100/ type: regex used=0
< expr node <addr-26> type=NAME left=(nil) right=(nil) save_last=0 [sample.bin] master=1
< __dmgetpmid: metric "qa.a" -> PMID 511.0.3
< __dmbind: bind metric[2] qa.a
< __dmtraverse: name="qa" added "qa.a"
< __dmgetpmid: metric "qa.b" -> PMID 511.0.4
< __dmbind: bind metric[3] qa.b
< __dmtraverse: name="qa" added "qa.b"
< __dmgetpmid: metric "qa.c" -> PMID 511.0.5
< __dmbind: bind metric[4] qa.c
< __dmtraverse: name="qa" added "qa.c"
< __dmgetpmid: metric "qa.d" -> PMID 511.0.6
< __dmbind: bind metric[5] qa.d
< __dmtraverse: name="qa" added "qa.d"
< __dmgetpmid: metric "qa.e" -> PMID 511.0.7
< __dmbind: bind metric[6] qa.e
< __dmtraverse: name="qa" added "qa.e"
< __dmgetpmid: metric "qa.a" -> PMID 511.0.3
< __dmgetpmid: metric "qa.b" -> PMID 511.0.4
< __dmgetpmid: metric "qa.c" -> PMID 511.0.5
< __dmgetpmid: metric "qa.d" -> PMID 511.0.6
< __dmgetpmid: metric "qa.e" -> PMID 511.0.7
< 
< qa.a
<     Data Type: 32-bit int  InDom: 29.2 0x7400002
<     Semantics: instant  Units: none
< 
< qa.b
<     Data Type: 32-bit int  InDom: 29.2 0x7400002
<     Semantics: instant  Units: none
< 
< qa.c
<     Data Type: 32-bit int  InDom: 29.2 0x7400002
<     Semantics: instant  Units: none
< 
< qa.d
<     Data Type: 32-bit int  InDom: 29.2 0x7400002
<     Semantics: instant  Units: none
< 
< qa.e
<     Data Type: 32-bit int  InDom: 29.2 0x7400002
<     Semantics: instant  Units: none
---
> expr node <addr-24> type=FILTERINST left=0xaaaac2ffc830 right=0xaaaac2ffcbf0 save_last=0

Expected results:
pminfo does not crash and test-case #688 succeeds

Additional info:
There is no reliable reproducer, however I am attaching an ABRT report from a crash, on aarch64 architecture, showing the code where the crash happens.

Comment 1 Jan Kurik 2020-06-19 13:21:50 UTC

Proposed fix: https://github.com/performancecopilot/pcp/pull/947

Comment 5 Jan Kurik 2020-07-13 07:53:51 UTC

Even there is no reliable reproducer, I have not seen this issue during regression testing any more (during approx 20 days of regression testing (including the pcp-testsuite)).
I am setting the SanityOnly flag and considering as verified.

Comment 8 errata-xmlrpc 2020-11-04 03:00:37 UTC

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 (pcp bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4684