RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1473968 [details]
error log

Description of problem:

PCP fails to merge an empty (non zero size) archive. In the end the archive merging is then completely skipped and also no compression and further housekeeping is done.

The non-empty archive could have been created by a start service restart and the disk was full to write more data.

Version-Release number of selected component (if applicable):
pcp-3.11.8-7.el7.x86_64            

How reproducible:
Issue occurring on customer end.

Expected results:

Expectation is that the merging works and skips the archive. Because with the current broken situation I as a user can also not proceed. And instead I am left with a system that is getting more full


Additional info:
attaching error log and archive to the case.


Currently customer has worked around the issue with a daily cron

# TODO Hilti workaround to make sure old files are deleted even when the pmlogger_daily fails during merging
05      0  *  *  *  pcp  find /var/log -maxdepth 1 -mtime +<%= @pmlogger_retention_days + 1 %> -type f -delete

Created attachment 1473971 [details]
archives

Hi, Any thoughts on this bug?

Hi Piyush,

(In reply to Piyush Bhoot from comment #3)
> Hi, Any thoughts on this bug?

There's definitely room for improvement here.  This note...

> The non-empty archive could have been created by a start service restart and the disk was full to write more data.

I don't completely follow.  Regular pmlogger service stop, start or restart actions will not cause archive corruption - however, filesystem fullness could.

There has been significant progress toward avoiding that situation in 7.6 however, so the priority of this BZ is less urgent than it otherwise would be.  We do plan further resilience work in pmlogger, however, so leaving this BZ open for when we tackle that.

cheers.