On 20/02/14 04:53, Chandana De Silva wrote:
> No luck
>
> ...
> $ pminfo -ft pmcd.client.whoami
>
> pmcd.client.whoami [optional identification information for clients of pmcd]
> inst [0 or "0"] value "hr1.m4u.com.au (192.168.7.155) pmie -b -h local:
> -l /var/log/pcp/pmie/hr1.m4u.com.au/healthstate.log -c healthstate.pmie"
> inst [3 or "3"] value "hr1.m4u.com.au (192.168.7.155) pmie -b -h local:
> -l /var/log/pcp/pmie/hr1.m4u.com.au/config.linux.log -c config.linux"
> inst [12 or "12"] value "hr1.m4u.com.au (192.168.7.155) pmie -b -h local:
> -l /var/log/pcp/pmie/hr1.m4u.com.au/pmie.log -c config.default"
> inst [13 or "13"] value ""
> inst [16 or "16"] value ""
One of the empty instances is pminfo, not sure about the other one.
How old is the pmlogger version on the system doing the logging? (this was
added with the -m option to pmlogger in Aug 2011 so would have escaped in PCP
2.5.9 or later).
For my test case, on the system being logged ...
kenj@vm04:~$ pminfo -f pmcd.client.whoami
pmcd.client.whoami
inst [1 or "1"] value "bozo.localdomain (192.168.1.100) pmlogger -h vm04 -r
-T24h10m -c config.default -m pmlogger_check 20140220.08.23"
inst [4 or "4"] value "vm04.localdomain (192.168.1.204) pmlogger -P -c
config.default -m pmlogger_check 20140220.08.25"
inst [7 or "7"] value "vm04.localdomain (192.168.1.204) pmie -b -h vm04 -l
/var/log/pcp/pmie/vm04/pmie.log -c config.default"
inst [8 or "8"] value ""
(inst 1 is our happy camper)
And on the system where pmlogger is running ...
kenj@bozo:~$ ps -ef | grep 'pmlogger.*vm0[4]'
pcp 4588 3530 0 08:23 pts/23 00:00:00 pmlogger -h vm04 -r -T24h10m -c
config.default -m pmlogger_check 20140220.08.23
|