G'day Chandana,
On 24/12/14 10:41, Chandana De Silva wrote:
> All,
>
> We are noticing what looks like a memory leak in pmcd on our older
> CentOS 5.5 machines, which are running Version 3.6.9.
3.6.9 dates from about Fri Oct 12 2012, so that is quite old. However, I don't
see any glaring pmcd-related memleak fixes since then.
Are you sure it is pmcd? What DSO PMDA's do you have configured?
> As an example, pmcd was restarted at ~ 22:00 hrs last night, and by
> 10:00 hrs today, Virtual Set Size had grown to 70 MB.
How big was it immediately after pmcd started? And 1 hr later after all the
pmlogger/pmie fetchs had been done at least once.
70MB may not be unusual for proc.psinfo.vsize (is that the metric you're using
to measure "Virtual Set Size"?) ... on my workstation after doing a pminfo -v
(to force every single metric to be instantiated), I see
kenj@bozo $ pminfo -f proc.psinfo.vsize | grep '[p]mcd'
inst [12896 or "012896 /usr/lib/pcp/bin/pmcd -T 3"] value 63200
and the units are Kbytes, so a little over 61MB.
I repeated the pminfo -v one hundred times, and there is only a small increase
...
> Our problem is that we have found difficulty in building any of the
> newer version of PCP against CentOS 5.5.
>
> I noticed on the PCP list you had managed to build for older CentOS
> versions. Is there a know recipe ?.
Pretty much the same recipe for every platform:
1. download and unpack the source
2. run qa/admin/check-vm (don't let the name confuse you) ... this sniffs about
for prereqs required to build PCP and run QA ... things marked [optional] in
the output you can safely ignore
3. ./Makepkgs
If this does not work, send mail to the list with Logs/pcp attached.
I am building OK for CentOS 5.11 ... I don't have 5.5 in my QA farm but could
spin one up (64bit I assume) if you're still having trouble.
|