pcp
[Top] [All Lists]

Re: [pcp] proc pmda oddness - qa 022

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] proc pmda oddness - qa 022
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Thu, 07 Nov 2013 12:23:43 +1100
Cc: "pcp@xxxxxxxxxxx >> PCP Mailing List" <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <123469235.21800488.1383786305811.JavaMail.root@xxxxxxxxxx>
References: <527A9322.6070107@xxxxxxxxxxxxxxxx> <123469235.21800488.1383786305811.JavaMail.root@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
On 07/11/13 12:05, Nathan Scott wrote:


----- Original Message -----
qa/022 is failing for me.

I have no clue how we could have got the proc pmda to the point where I
can retrieve proc.psinfo.stime for pid 017676 but cannot retrieve
proc.psinfo.utime for the same pid.

Anyone else seeing this?

  From 022.full ...


Is it only the part of the test where an indom profile is in place, that
fails, or are some values always missing for the utime metric?

--- Fetch Over Restricted Instance Domain ... ---
pmResult dump from 0x8051910 timestamp: 1383612667.698941 11:51:07.698
numpmid: 4
    3.8.13 (proc.psinfo.utime): numval: 1 valfmt: 0 vlist[]:
      inst [17649 or "017649 sh 022"] value 30
    3.8.14 (proc.psinfo.stime): numval: 2 valfmt: 0 vlist[]:
      inst [17649 or "017649 sh 022"] value 10
      inst [17676 or "017676 src/proc_test -h unix: proc.psinfo.utime
proc.psinfo.stime proc.memory.rss proc.memory.size"] value 0

Since utime and stime are extracted from the same file, and the PMID
item component is used to identify the right field (column), its very
tough to see how 13 cannot be found, but 14 is!  (linux_proc/pmda.c,
line 999)

 From my previous test run .full, where all OK ... looks as expected.

--- Fetch Over Restricted Instance Domain ... ---
pmResult dump from 0x14d0080 timestamp: 1383274005.850216 13:46:45.850 numpmid: 
4
   3.8.13 (proc.psinfo.utime): numval: 2 valfmt: 1 vlist[]:
     inst [26223 or "026223 sh 022"] value 10
     inst [26247 or "026247 src/proc_test -h unix: proc.psinfo.utime 
proc.psinfo.stime proc.memory.rss proc.memory.size"] value 10
   3.8.14 (proc.psinfo.stime): numval: 2 valfmt: 1 vlist[]:
     inst [26223 or "026223 sh 022"] value 0
     inst [26247 or "026247 src/proc_test -h unix: proc.psinfo.utime 
proc.psinfo.stime proc.memory.rss proc.memory.size"] value 30
   3.9.1 (proc.memory.rss): numval: 2 valfmt: 0 vlist[]:
     inst [26223 or "026223 sh 022"] value 1736
     inst [26247 or "026247 src/proc_test -h unix: proc.psinfo.utime 
proc.psinfo.stime proc.memory.rss proc.memory.size"] value 4252
   3.9.0 (proc.memory.size): numval: 2 valfmt: 0 vlist[]:
     inst [26223 or "026223 sh 022"] value 106492
     inst [26247 or "026247 src/proc_test -h unix: proc.psinfo.utime 
proc.psinfo.stime proc.memory.rss proc.memory.size"] value 90292
--- End Fetch Over Restricted Instance Domain ... ---


Bizzaro.

--
Nathan


Agreed.

But I have the same failure now here ...

Host        PCP      CPU     Operating System
----------- -------- ------  ------------------
vm07        unknown  x86_64  Debian 6.0.5

and it is ONLY the restricted indom case that is failing.

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