| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] proc pmda cgroups/labels changes |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 7 Nov 2013 20:20:29 -0500 (EST) |
| Cc: | PCP Mailing List <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <527C1116.4050401@xxxxxxxxxxxxxxxx> |
| References: | <527C1116.4050401@xxxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | WvnE9CSKO98Rfvge7y59Khm1XFqg6w== |
| Thread-topic: | proc pmda cgroups/labels changes |
----- Original Message -----
> Can anyone explain a recent change that produces this
>
> $ pminfo -v proc.psinfo
> proc.psinfo.cgroups: Unknown or illegal instance identifier
> proc.psinfo.labels: Unknown or illegal instance identifier
>
> on some systems and not others?
This is exporting /proc/PID/cgroup and /proc/PID/attr/current
values. It looks like systems where these files are empty or
otherwise return an error on open, will cause the above inst
error. I guess thats because all the proc.psinfo metrics use
the same ("all processes") indom.
> If this is expected, I'll just fix the filter in qa/359.
It can be safely filtered, thanks.
cheers.
--
Nathan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pmcd config file migration after upgrade issue, Nathan Scott |
|---|---|
| Next by Date: | pcp updates: small fixes, net hw_addr, Nathan Scott |
| Previous by Thread: | proc pmda cgroups/labels changes, Ken McDonell |
| Next by Thread: | Fwd: Re: [pcp] proc pmda oddness - qa 022, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |