What were you trying to do that didn't work?
We have extracted the large pcp logs to the problem window using pmlogextract command and then when we do #pcp pidstat against the extracted archive file. It reports below error:
~~~
pcp pidstat -z -a 20251130.05.59.0.extracted| more
Error: not all required metrics are available
Missing ['kernel.uname.machine', 'kernel.uname.nodename', 'kernel.uname.release', 'kernel.uname.sysname']
~~~
What is the impact of this issue to you?
It takes lot of time if we run pcp pidstat against a large pcp logs. Hence we extract the problem logs (using pmlogextract) but pcp pidstat doesn't work against the reduced archive file.
Please provide the package NVR for which the bug is seen:
Latest PCP package on all RHEL versions:
~~~
rpm -qa | grep pcp
pcp-selinux-6.3.7-5.el10.x86_64
pcp-conf-6.3.7-5.el10.x86_64
pcp-libs-6.3.7-5.el10.x86_64
pcp-6.3.7-5.el10.x86_64
python3-pcp-6.3.7-5.el10.x86_64
pcp-pmda-nfsclient-6.3.7-5.el10.x86_64
pcp-pmda-openmetrics-6.3.7-5.el10.x86_64
pcp-system-tools-6.3.7-5.el10.x86_64
pcp-pmda-dm-6.3.7-5.el10.x86_64
pcp-doc-6.3.7-5.el10.noarch
pcp-zeroconf-6.3.7-5.el10.x86_64
~~~
How reproducible is this bug?:
Easily and 100% reproducible
Steps to reproduce
1] Install the pcp-zeroconf and let it store the pcp logs in an archive.
2] Try to extract or reduce the window to smaller size using pmlogextract
~~~
pmlogextract --hostzone -S"Nov 30 06:10" -T"Nov 30 06:50" 20251130.05.59.0 20251130.05.59.0.extracted
Note: timezone set to local timezone of host "cjain-rhel9-moccasin-shrimp-17" from archive
~~~
3] Run pcp pidstat against the extracted file:
~~~
pcp pidstat -z -a 20251130.05.59.0.extracted| more
Error: not all required metrics are available
Missing ['kernel.uname.machine', 'kernel.uname.nodename', 'kernel.uname.release', 'kernel.uname.sysname']
~~~
Expected results
it should not report that error and work as usal.
Actual results
Reporting below error:
~~~
pcp pidstat -z -a 20251130.05.59.0.extracted| more
Error: not all required metrics are available
Missing ['kernel.uname.machine', 'kernel.uname.nodename', 'kernel.uname.release', 'kernel.uname.sysname']
~~~