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 1062443

Summary:

gfs2 PMDA: Error Parsing ASCII PMNS: pmcpp returned non-zero exit status

Product:

Red Hat Enterprise Linux 7

Reporter:

Andrew Price <anprice>

Component:

pcp

Assignee:

Nathan Scott <nathans>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Miloš Prchlík <mprchlik>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

7.0

CC:

fche, mbenitez, mcermak, mgoodwin, mprchlik, pevans, swhiteho

Target Milestone:

Keywords:

Reopened

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-06-13 12:15:47 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
Updates to documentation to mention that pmcd should be running before install attempt	none
Update to Install script to check pmcd is running	none

Description Andrew Price 2014-02-07 00:05:10 UTC

Description of problem:

Attempting to install the gfs2 PMDA on my RHEL7 machine, using the instructions in the pmdagfs2 man page, it gave the following error:

[root@curie-01 ~]# cd /var/lib/pcp/pmdas/gfs2/
[root@curie-01 gfs2]# ./Install 
You will need to choose an appropriate configuration for installation of
the "gfs2" Performance Metrics Domain Agent (PMDA).

  collector     collect performance statistics on this system
  monitor       allow this system to monitor local and/or remote systems
  both          collector and monitor configuration for this system

Please enter c(ollector) or m(onitor) or b(oth) [b] b
pmcpp: root[5]: #include <stdpmid>
pmcpp: Error: Cannot open file for #include
Error Parsing ASCII PMNS: pmcpp returned non-zero exit status
newhelp: pmLoadNameSpace: Problems parsing PMNS definitions
Updating the Performance Metrics Name Space (PMNS) ...
pmnsadd: cannot find PMNS file ""
Install: failed to add the PMNS entries for "gfs2" ...

total 72
-rw-r--r-- 1 root root  4660 Feb  6 17:53 gfs2
-rw-r--r-- 1 root root  1093 Jan 29 03:38 Makefile
-rwxr-xr-x 1 root root  4011 Jan 29 03:38 Make.stdpmid
-rwxr-xr-x 1 root root  8080 Jan 29 03:38 Rebuild
-rw-r--r-- 1 root root  1362 Jan 29 03:38 root_jbd2
-rw-r--r-- 1 root root 15562 Jan 29 03:38 root_linux
---------- 1 root root     0 Feb  6 17:53 root.lock
-rw-r--r-- 1 root root   103 Jan 29 03:38 root_mmv
-rw-r--r-- 1 root root  2474 Jan 29 03:38 root_pmcd
-rw-r--r-- 1 root root  3228 Jan 29 03:38 root_proc
-rw-r--r-- 1 root root  5358 Jan 29 03:38 root_xfs
-rw-r--r-- 1 root root    76 Jan 29 03:38 stdpmid.local
-rw-r--r-- 1 root root  1456 Jan 29 03:38 stdpmid.pcp

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

pcp-3.8.10-4.el7.x86_64

How reproducible:

Every time I run ./Install

Steps to Reproduce: See above.

Actual results: See above.

Expected results: No error.

Comment 2 Nathan Scott 2014-02-07 00:25:08 UTC

Hi Andrew - thanks for reporting it - if you do:

    # service pmcd start

before attempting the ./Install, does the installation proceed correctly?

Comment 3 Andrew Price 2014-02-07 00:51:12 UTC

Ah yes, it does. I wasn't aware that pmcd had to be started beforehand. Feel free to close this as PEBKAC or maybe switch it to a documentation bug if you think it's worth it. Thanks!

Comment 4 Nathan Scott 2014-02-07 01:06:58 UTC

Thanks for checking.  Yeah, the failure mode of the script leaves alot to be desired in this case.  I'll look into improving that, so will keep this BZ open until I've done that.

cheers.

Comment 5 Paul Evans 2014-02-07 12:11:10 UTC

I've posted two patches to the pcp mailing list, An update to the documentation (README file and the man page) for the pmdagfs2 along with a patch which checks if pmcd is running before attempting to install the pmda.

Comment 6 Paul Evans 2014-02-07 12:12:22 UTC

Created attachment 860469 [details]
Updates to documentation to mention that pmcd should be running before install attempt

Comment 7 Paul Evans 2014-02-07 12:13:16 UTC

Created attachment 860470 [details]
Update to Install script to check pmcd is running

Comment 8 Andrew Price 2014-02-07 12:50:28 UTC

Thanks for working on this Paul. Just one nit:

    +ps cax | grep pmcd > /dev/null
    +if [ $? -eq 0 ]; then

isn't a reliable way to check whether a service is running. Ideally you want a client to try to connect to it. Maybe use something like this instead:

    if pminfo -f pmcd.version; then

Comment 9 Nathan Scott 2014-02-10 23:03:46 UTC

This issue is now tackled by upstream commit 0b1500ff (below).  Following on from Andrews comment #3 here, I'll close this bug now & mark it as "fixed upstream" (i.e. it will percolate down into RHEL in due course, if I've interpreted that state correctly this time!)

commit 0b1500ff74341c54c3da4412eb8ee8db9c58cf41
Author: Nathan Scott <nathans>
Date:   Tue Feb 11 09:54:07 2014 +1100

    Allow PMDA Install scripts to be run even when pmcd is stopped.
    
    Following the Install recipe from the GFS2 PMDA man page, users
    can run into difficulty if pmcd is not running first.  There's
    no mention of that, and the error message is cryptic.  This fix
    extends the generic PMDA installation process to allow any PMDA
    to kick-start the pmcd process if it needs to.  The one wrinkle
    there is a chicken-and-egg with the namespace setup, but that's
    tackled via addition of a Rebuild call in the right spot.
    
    Reported by Andrew Price, tested by Paul Evans, myself and now
    also PCP QA test 755.
    
    Resolves Red Hat bug #1062443.

Comment 10 Steve Whitehouse 2014-02-18 15:01:09 UTC

Should this not be blocker rather than exception, since it is a bug fix?

Comment 12 Miloš Prchlík 2014-02-20 09:59:26 UTC

Verified for build pcp-3.8.10-6.el7.

Comment 13 Ludek Smid 2014-06-13 12:15:47 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.