| To: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Fetching proc data from a remote host |
| From: | Chandana De Silva <chandana@xxxxxxxxxxxxx> |
| Date: | Tue, 30 Dec 2014 13:39:35 +1100 |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <54A1F9FC.2060302@xxxxxxxxxx> |
| Organization: | Chandana De Silva |
| References: | <1419894543.5699.4.camel@xxxxxxxxxxxxx> <54A1F9FC.2060302@xxxxxxxxxx> |
| Reply-to: | chandana@xxxxxxxxxxxxx |
Hello Mark,
Thanks for your reply.
The proc pmda is running as root.
$ ps aux | grep proc
root 15828 0.0 0.3 42416 1764 ? S 09:52 0:01
/var/lib/pcp/pmdas/proc/pmdaproc -d 3
And, I can view the data on the host.
$ pminfo -f proc.psinfo.vsize
proc.psinfo.vsize
inst [1 or "000001 init [3]"] value 10352
inst [2 or "000002 (migration/0)"] value 0
inst [3 or "000003 (ksoftirqd/0)"] value 0
What I can't do is view this from another machine (which is running pmlogger).
On Tue, 2014-12-30 at 12:03 +1100, Mark Goodwin wrote:
> most likely pmdaproc on the remote host is running as the pcp user,
> which doesn't have access to all of the /proc/<pid>/... data for users
> other than pcp. The proc.nprocs metric is extracted from /proc/stat,
> which doesn't have such access restrictions (world readable).
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] Fetching proc data from a remote host, Mark Goodwin |
|---|---|
| Next by Date: | Re: [pcp] Fetching proc data from a remote host, Ken McDonell |
| Previous by Thread: | Re: [pcp] Fetching proc data from a remote host, Mark Goodwin |
| Next by Thread: | Re: [pcp] Fetching proc data from a remote host, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |