1673996 – pcp-atopsar -A fails to display any values

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 1673996 - pcp-atopsar -A fails to display any values

Summary: pcp-atopsar -A fails to display any values

Keywords:
Status:	CLOSED DUPLICATE of bug 1647308
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pcp
Sub Component:
Version:	7.7
Hardware:	All
OS:	Linux
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Lukas Berk
QA Contact:	qe-baseos-tools-bugs
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2019-02-08 16:55 UTC by Charles Haithcock
Modified:	2019-05-17 00:40 UTC (History)
CC List:	5 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2019-05-17 00:40:14 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Charles Haithcock 2019-02-08 16:55:06 UTC

Description of problem:

When provided with an archive file, pcp-atopsar -A seems to hang and not produce anything other than an error regarding "no per-process network counters available.....". Other pcp-atopsar options work however, such as -c and -m


Version-Release number of selected component (if applicable):

 r7 # rpm -q pcp
pcp-4.1.0-5.el7_6.x86_64



How reproducible:

Always


Steps to Reproduce:
1. Install pcp-zeroconf
2. Wait for metrics to accumulate
3. pcp -a /var/log/pcp/pmlogger/<HOSTNAME>/<DATA> atopsar -A

Actual results:

 r7 # pcp -a /var/log/pcp/pmlogger/r7/20190208.09.30 atopsar -A

r7  3.10.0-957.5.1.el7.x86_64  #1 SMP Wed Dec 19 10:46:58 EST 2018  x86_64  2019/02/08

-------------------------- analysis date: 2019/02/08 --------------------------

09:30:50    pid command  net% |   pid command  net% |   pid command  net%_top3_
09:30:50  ......................... logging restarted .........................

09:31:10    pid command  net% |   pid command  net% |   pid command  net%_top3_
09:31:10  no per-process network counters available.....
^C


Hangs indefinitely here (thus the ^C)


Expected results:

Rolling metrics similar to running it live without an archive file or in batches of metrics like in sar data. 

Additional info:

Comment 2 Lukas Berk 2019-03-13 15:03:30 UTC

Fixed upstream in commit:

commit 82901e84ee150c17e37167bf0389aebcb7e2fab8 (HEAD -> master)
Author: Lukas Berk <lberk>
Date:   Tue Mar 12 17:18:17 2019 -0400

    atopsar: rhbz1673996 fix -A for replying from archive
    
    Atopsar and atop's main loops fundamentally loop over the data in
    different ways.  We've had to adjust them accordingly.
    
    In atop's "main" engine(), we iterate over the entirety of the data
    from time t0 -> tX, displaying all data categories (C1, C2, CY) as we
    get them.
    
    ie;
    
    t0  C1value0 C2value0 ... CYvalue0
    t1  C1value1 C2value1 ... CYvalue1
    t2  C1value2 C2value2 ... CYvalue2
    ...
    tX  C1valueX C2valueX ... CYvalueX
    
    Using the archive reply in atopsar, we instead iterate over each
    category requested, going from t0 -> tX for C1, then t0 -> tX for C2,
    etc.
    
    ie;
    
    C1
    t0  value1@t0 value1@t0 ... value1@t0
    t1  value2@t1 value2@t1 ... value2@t1
    ...
    tX  value2@tX value2@tX ... value2@tX
    
    This patch modifies the engine loop to catch when we need to interate
    to the next value, or reset our loop to the start of the archive to
    loop over the values for the next category.
    
    qa/1390 - new test for -A option
    qa/785  - update output

Comment 3 Nathan Scott 2019-05-17 00:40:14 UTC

Resolved as part of the the 7.7 rebase.

*** This bug has been marked as a duplicate of bug 1647308 ***

Note You need to log in before you can comment on or make changes to this bug.