pcp
[Top] [All Lists]

Re: [pcp] problem with containers support and qa/977

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] problem with containers support and qa/977
From: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Sat, 28 Feb 2015 15:43:20 +1100
Cc: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <00a401d052cc$4349f230$c9ddd690$@internode.on.net>
References: <00a401d052cc$4349f230$c9ddd690$@internode.on.net>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
On 02/28/2015 07:30 AM, Ken McDonell wrote:
This is on opensuse13.1 ...

kenj@vm24:~/src/pcp/qa$ pminfo -f pmcd.feature.containers

pmcd.feature.containers
     value 1
kenj@vm24:~/src/pcp/qa$ src/grind_ctx -h local:?container=fe4564ddf901
Iteration 4
pmNewContext(host=local:?container=fe4564ddf901): Operation not supported

Because pmcd.feature.contatiners is 1, qa/977 is run but immediately trips
over the grind_ctx error.

I'm seeing this on FC19 but not on RHEL7.1. Both were built from
top-of-tree source using Makepkgs.

Here's RHEL7.1, which succeeds :

[root@ocean ~]# pminfo -DCONTEXT --container 6ea85ce8e3c4 -f hinv.ncpu
__pmSetSocketIPC: fd=3
IPC table fd(PDU version):
__pmDecodeXtendError: got error PDU (code=0, datum=1459618050, version=2)
__pmSetVersionIPC: fd=3 version=2
IPC table fd(PDU version): 3(2,1)
__pmSendCreds: #0 = 1020040
__pmSetDataIPC: fd=3 data=0x7fff0b4df7c0(sz=32)
IPC table fd(PDU version): 3(2,1)
connect.c:__pmConnectHandshake container="6ea85ce8e3c4" [12]
__pmConnectPMCD(/var/run/pcp/pmcd.socket): pmcd connection path=/var/run/pcp/pmcd.socket fd=3 PDU version=2
IPC table fd(PDU version): 3(2,1)
pmNewContext(1, local:) -> 0
Dump Contexts: current context = 0
Context[0] host /var/run/pcp/pmcd.socket: pmcd=CONNECTED profile=NOT_SENT fd=3 refcnt=1 flags=4000 origin=0.000000 delta=0
Dump Instance Profile state=INCLUDE, 0 profiles
pmWhichContext() -> 0, cur=0
pmWhichContext() -> 0, cur=0
pmWhichContext() -> 0, cur=0
pmWhichContext() -> 0, cur=0
pmWhichContext() -> 0, cur=0
pmWhichContext() -> 0, cur=0

hinv.ncpu
    value 2

And here's FC19, which fails :

[mgoodwin@fletch pcp]$ pminfo -DCONTEXT --container cee2a80b5f61 -f hinv.ncpu
__pmSetSocketIPC: fd=3
IPC table fd(PDU version):
__pmDecodeXtendError: got error PDU (code=0, datum=1073742082, version=2)
__pmSetVersionIPC: fd=3 version=2
IPC table fd(PDU version): 3(2,1)
__pmSendCreds: #0 = 1020040
__pmSetSocketIPC: fd=3
IPC table fd(PDU version):
__pmDecodeXtendError: got error PDU (code=0, datum=1073742082, version=2)
__pmSetVersionIPC: fd=3 version=2
IPC table fd(PDU version): 3(2,1)
__pmSendCreds: #0 = 1020040
__pmConnectPMCD(/var/run/pcp/pmcd.socket): pmcd connection port=44321 failed: Operation not supported
pmNewContext(1, local:) -> -95, curcontext=-1
pminfo: Cannot connect to PMCD on host "local:": Operation not supported
[mgoodwin@fletch pcp]$ pminfo -f pmcd.feature

pmcd.feature.secure
    value 0

pmcd.feature.compress
    value 0

pmcd.feature.ipv6
    value 1

pmcd.feature.authentication
    value 0

pmcd.feature.creds_required
    value 0

pmcd.feature.unix_domain_sockets
    value 1

pmcd.feature.service_discovery
    value 1

pmcd.feature.containers
    value 1

Both systems have just one container running with the given Id.
The only difference seems to be that pmcd.feature.authentication
is 0 in the failing case and 1 in the succeeding case. Maybe there's
yet another missing build dep that's been silently configured away?

I'll try and debug it some more later this week-end.

Regards
-- Mark




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