----- "Greg Siekas" <greg.siekas@xxxxxxxxxx> wrote:
> I’m running pcp 3.3.3-1 under SLES9 SP4 x86_64. I’m found that if I do
> a pminfo –F –h <hostname> the pmcd dies on the client. The pmcd.log
> shows the following.
If you run:
for m in `pminfo -h <hostname>`; do
echo $m
pminfo -F -h <hostname> $m
done
It should tell us which specific metric is causing the problem.
Probably one of the newer NUMA metrics, at a guess, mem.numa.xxx,
so could you also send copies of your
/sys/devices/system/node/node*/{meminfo,numastat}
files please?
To debug further, if you stop pmcd, then run "gdb --args pmcd -f" on
the failing host, when it gets SIGSEGV it should stop in the failing
code (a backtrace - gdb "bt" command output - would be great, then).
cheers.
--
Nathan
|