Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
5min 19.175s pmlogger_daily_report.service
45.250s pmlogger_daily.service
6.815s pmlogger.service
1.480s pmlogger_check.service
76ms pmlogger_daily-poll.service
38ms pmlogger_daily_report-poll.service
pmlogger.service is declared as dependency on multi-user.target, so it part of the normal boot. Anything above a few seconds for a service that runs on every boot is just bad. Also, a few seconds is noticeable for users.
If we override all pmlogger*.service (pmlogger_daily-poll.service, pmlogger_daily_report-poll.service, pmlogger_daily_report.service, pmlogger_daily.service, pmlogger.service, pmlogger_check.service) and change Type=notify and deleted line "RequiredBy=pmlogger.service" from pmlogger_check.service then result is:
1min 30.319s pmlogger_daily_report.service
3.512s pmlogger_check.service
148ms pmlogger.service
82ms pmlogger_daily-poll.service
39ms pmlogger_daily_report-poll.service
Version-Release number of selected component (if applicable):
pcp-4.3.2-2.el8.x86_64
How reproducible:
Need to install pcp-4.3.2-2.el8.x86_64 and enable pmlogger*.service.
Actual results:
pmlogger_daily_report.service is taking a long time to start during boot
Expected results:
pmlogger_daily_report.service should not take so long time to start during boot.
Additional info:
The same kind of related bug was raised for Fedora : https://bugzilla.redhat.com/show_bug.cgi?id=1737091
The version of "pcp" package is different in both the Bugzilla and I believe the issues are different.
Is it possible to open this Bugzilla and look into this issue once?
Dushyant, there were quite a few issues resolved as part of that BZ, including issues around pmlogger_daily_report and other pmlogger scripts inducing long delays around archive (de-)compression. This issue is definitely resolved there.
Please try out pcp-5.0.2-2 with the 8.2 beta (publically available in a week or so AIUI).
cheers.
Description of problem: 5min 19.175s pmlogger_daily_report.service 45.250s pmlogger_daily.service 6.815s pmlogger.service 1.480s pmlogger_check.service 76ms pmlogger_daily-poll.service 38ms pmlogger_daily_report-poll.service pmlogger.service is declared as dependency on multi-user.target, so it part of the normal boot. Anything above a few seconds for a service that runs on every boot is just bad. Also, a few seconds is noticeable for users. If we override all pmlogger*.service (pmlogger_daily-poll.service, pmlogger_daily_report-poll.service, pmlogger_daily_report.service, pmlogger_daily.service, pmlogger.service, pmlogger_check.service) and change Type=notify and deleted line "RequiredBy=pmlogger.service" from pmlogger_check.service then result is: 1min 30.319s pmlogger_daily_report.service 3.512s pmlogger_check.service 148ms pmlogger.service 82ms pmlogger_daily-poll.service 39ms pmlogger_daily_report-poll.service Version-Release number of selected component (if applicable): pcp-4.3.2-2.el8.x86_64 How reproducible: Need to install pcp-4.3.2-2.el8.x86_64 and enable pmlogger*.service. Actual results: pmlogger_daily_report.service is taking a long time to start during boot Expected results: pmlogger_daily_report.service should not take so long time to start during boot. Additional info: The same kind of related bug was raised for Fedora : https://bugzilla.redhat.com/show_bug.cgi?id=1737091