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.
Bug 1780073 - pmlogger.service times out on first start
Summary: pmlogger.service times out on first start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcp
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: 8.0
Assignee: Mark Goodwin
QA Contact: Jan Kurik
URL:
Whiteboard:
: 1789306 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-05 11:15 UTC by Patrik Hagara
Modified: 2023-12-15 17:02 UTC (History)
8 users (show)

Fixed In Version: pcp-5.0.2
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:40:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-31013 0 None None None 2023-04-11 16:37:57 UTC
Red Hat Product Errata RHBA-2020:1628 0 None None None 2020-04-28 15:41:05 UTC

Description Patrik Hagara 2019-12-05 11:15:04 UTC 
Description of problem:
Starting pmlogger service using `systemctl start pmlogger.service`
fails with a timeout error when started for the first time after
installation (before directory trees are created).

This breaks our (Cluster QE) test automation as we use pcp to collect test runtime perf data.

Please see bz#1721223 (equivalent Fedora BZ) for details, specifically https://bugzilla.redhat.com/show_bug.cgi?id=1721223#c26 for a root cause analysis.


Version-Release number of selected component (if applicable):
[root@virt-160 ~]# rpm -q pcp systemd
pcp-5.0.1-1.el8.x86_64
systemd-239-19.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. install a RHEL-8.2.0 compose (tested with `RHEL-8.2.0-20191125.n.0`)
2. `yum install pcp`
3. `systemctl start pmlogger`

Actual results:
Fails with a timeout, returns non-zero exit code.
Systemd then automatically restarts the service, which succeeds.

Expected results:
Successful start on first try.

Additional info:
see bz#1721223 for Fedora BZ with more details
Comment 1 Jan Kurik 2019-12-05 15:16:01 UTC 
I was also observing this behaviour during the last days, testing the pcp-5.0.1-1 build. However I was not able to reproduce this reliably. It happens only sometimes, even on fresh installations.
As a temporary workaround I set "TimeoutSec" to "240" seconds (it is set by default to 120) in /usr/lib/systemd/system/pmlogger.service file.
Comment 2 Mark Goodwin 2019-12-05 22:27:11 UTC 
This should be fixed in pcp-5.0.2 (not yet released) with the following upstream commit :

commit 0f3a1fa7d0d7a898acf2ee4a6f23b626d4fb7362
Author: Mark Goodwin <mgoodwin>
Date:   Wed Nov 13 09:50:57 2019 +1100

    logutil: fix pmlogger service timeout on virgin install
    
    RHBZ#1721223 - pmlogger.service: Failed with result 'timeout'
    PCP GH#792
    
    Do not invoke pmlogger_daily -K to compress archives from pmlogger_check
    on a virgin install - it confuses systemd's Type=forking exit status
    checks, resulting in the pmlogger service timing out.  There is nothing
    to compress anyway!
    
    This fixes the installation issues reported by Marko in BZ#1721223
    but does not update the service configs - they are still Type=forking
    and so there will still be some (benign) complaints from systemd as
    reported in the BZ.
Comment 4 Nathan Scott 2020-01-10 02:57:34 UTC 
*** Bug 1789306 has been marked as a duplicate of this bug. ***
Comment 5 Jan Kurik 2020-01-13 15:11:20 UTC 
@Patrik: May I ask you please to verify the new PCP build [1] in  your environment ? I am unable to reproduce it any more, using the new build [1].

[1] https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1034946
Comment 6 Patrik Hagara 2020-01-15 10:44:23 UTC 
We do not see pmlogger.service start timeouts on fresh installs anymore.

> [root@virt-008 ~]# rpm -q pcp
> pcp-5.0.2-2.el8.x86_64
> [root@virt-008 ~]# journalctl -u pmlogger
> -- Logs begin at Tue 2020-01-14 11:11:13 CET, end at Wed 2020-01-15 11:40:09 CET. --
> Jan 14 11:22:21 virt-008.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Starting Performance Metrics Archive Logger...
> Jan 14 11:22:22 virt-008.cluster-qe.lab.eng.brq.redhat.com pmlogger[11877]: Starting pmlogger ...
> Jan 14 11:22:22 virt-008.cluster-qe.lab.eng.brq.redhat.com systemd[1]: pmlogger.service: Can't open PID file /run/pcp/pmlogger.pid (yet?) after start: No such file or directory
> Jan 14 11:22:22 virt-008.cluster-qe.lab.eng.brq.redhat.com systemd[1]: pmlogger.service: New main PID 12254 does not belong to service, and PID file is not owned by root. Refusing.
> Jan 14 11:22:22 virt-008.cluster-qe.lab.eng.brq.redhat.com systemd[1]: pmlogger.service: New main PID 12254 does not belong to service, and PID file is not owned by root. Refusing.
> Jan 14 11:22:24 virt-008.cluster-qe.lab.eng.brq.redhat.com systemd[1]: pmlogger.service: Supervising process 12393 which is not our child. We'll most likely not notice when it exits.
> Jan 14 11:22:24 virt-008.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Started Performance Metrics Archive Logger.
> Jan 14 11:23:34 virt-008.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Stopping Performance Metrics Archive Logger...
> Jan 14 11:23:35 virt-008.cluster-qe.lab.eng.brq.redhat.com pmlogger[13457]: Stopping pmlogger ...
> Jan 14 11:23:35 virt-008.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Stopped Performance Metrics Archive Logger.
Comment 7 Jan Kurik 2020-01-15 10:51:40 UTC 
Thanks Partik!
Comment 9 errata-xmlrpc 2020-04-28 15:40:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1628
Note You need to log in before you can comment on or make changes to this bug.