Nathan,
On 11/10/14 1:26 AM, Nathan Scott wrote:
I have a fix for 022 & will do 943 - they're fixable using sort(1) to produce
deterministic output.
I'm also seeing 580 fail, looks probably related:
$ diff 580.out 580.out.bad
7,9c7
< pm*InDom: inst=[1] iname=<ONE init> reverse lookup: inst=[1]
< pmGetInDom:
< [1] <ONE init>
---
Error: Unknown or illegal metric identifier
I'll dig into it later in the week if its not failing elsewhere and/or not
reproducible.
I think I'm ok with fixing everything but this. I don't understand why
it is failing. I put some debugging into the indom.c test and all
queries into the proc pmda, even non-dynamic elements, return bogus
information from pmLookupName:
************
[vagrant@pcptest src]$ ./indom -h unix: -i 1 proc.psinfo.pid
proc.psinfo.pid:
running proc.psinfo.pid
pmID (d,c,i): 511, 3, 0
failed 2
Error: Unknown or illegal metric identifier
*************
pmLookupName returns successfully (non-error), but all proc queries have
the domain,cluster,item values of 511,3,0.
But, strangely, the following works fine:
*************
[vagrant@pcptest src]$ pmval -h unix: -i 1 proc.psinfo.pid
metric: proc.psinfo.pid
host: pcptest
semantics: discrete instantaneous value
units: none
samples: all
1
*************
My guess is that I'm not building the tree properly, but I'm not sure
what is missing.
Thanks
Martins
|