pcp
[Top] [All Lists]

Re: pmdagfs2: Updates to documentation and install script

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: pmdagfs2: Updates to documentation and install script
From: Paul Evans <pevans@xxxxxxxxxx>
Date: Sun, 09 Feb 2014 23:41:09 +0000
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <540859557.22515469.1391813850484.JavaMail.root@xxxxxxxxxx>
References: <52F4C82E.1050007@xxxxxxxxxx> <540859557.22515469.1391813850484.JavaMail.root@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
Hi Nathan,

On 02/07/2014 10:57 PM, Nathan Scott wrote:
The attached patch is where I was at - it looks to see if the
root namespace file exists before attempting to add the new sub
tree, and if not, Rebuilds it and flags pmcd to be started later
on.  I've not tested it though, and its something that needs a
few more eyes on it (affects every PMDA install).  If you could
look over it and give it a whirl, that'd be much appreciated.

I've taken a  quick looksee at the patch you provided and had
to make some slight alterations in order to get it to allow an
error free PMDA install with this scenario on my RHEL 7 machine.
With the alterations the attached patch seems to work well and
the PMDA installed works when PMCD is later started.

After changing the logic of the test for Rebuild to continue
if found I ran into an issue where PMCPP would error and bail
whilst parsing a PMDA root (PMDADIR/root) if it included
stdpmid. For lack of it existing yet.

I found that generating an initial copy of stdpmid using the
available Make.stdpmid before calling Rebuild allowed the PMDA
install to continue and complete successfully with only a verbal
warning for being unable to lock the root ($PCP_VAR_DIR/pmns/
root.lock). Becauseit does not exist yet.

--- Terminal output ----

[root@localhost 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]
Updating the Performance Metrics Name Space (PMNS) ...
lockpmns: Warning: Unable to acquire lock (root.lock)
                   after 120 seconds ... continuing anyway
Terminate PMDA if already installed ...
Updating the PMCD control file, and notifying PMCD ...
Rebuilding PMNS ...
Starting pmcd ...
Check gfs2 metrics have appeared ... 203 metrics and 193 values

--- Terminal output ----

Cheers,

Paul

Attachment: pmdaproc-ammed.patch
Description: Text Data

<Prev in Thread] Current Thread [Next in Thread>