pcp
[Top] [All Lists]

Re: Containers analysis with PCP

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: Containers analysis with PCP
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 9 Feb 2015 19:32:13 -0500 (EST)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <y0m7fvr3tem.fsf@xxxxxxxx>
References: <2100915892.5240937.1422867358164.JavaMail.zimbra@xxxxxxxxxx> <768474811.5242777.1422867576642.JavaMail.zimbra@xxxxxxxxxx> <y0m7fvr3tem.fsf@xxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: jw6c/TYQa7yQMgk3HnolFFRk/QxA7A==
Thread-topic: Containers analysis with PCP

----- Original Message -----
> > [...]
>  Please don't forget to address earlier review comments in [1].

The review was ~2 weeks out of date when sent & the one/two issues there
were fixed already, independently.  I see nothing needing further action
there.

Feel free to revisit & reassess with current code (objectively, please -
patches and QA tests will help you more than opinions about design docs)
if you think there's anything worth doing there still.

> Also, on my x86-64 fedora21 box running the 3.10.2 build, I still can't get
> any pcp client --container ops working, e.g.,
> 
> % pmprobe -I --container=compassionate_archimedes  network.interface.up
> network.interface.up 4-12366 IPC protocol failure (pmGetInDom)

This is not reproducible here - can you either debug & send a fix and test
case, or go into more detail about your containers + pcp setup such that
someone can help you?  (incl. pmcd.conf, pmcd.log, values for containers
metrics & detailed go-to-woe instructions for the Docker commands you're
using).

Can you also describe what you have already in terms of diagnosing this?

cheers.

--
Nathan

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