Bug 1780073
| Summary: | pmlogger.service times out on first start | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Patrik Hagara <phagara> |
| Component: | pcp | Assignee: | Mark Goodwin <mgoodwin> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Kurik <jkurik> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | agerstmayr, batkisso, cluster-qe, duge, jkurik, mgoodwin, nathans, patrickm |
| Target Milestone: | rc | Keywords: | Regression, TestBlocker, Triaged |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pcp-5.0.2 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-28 15:40:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Patrik Hagara
2019-12-05 11:15:04 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.
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.
*** Bug 1789306 has been marked as a duplicate of this bug. *** @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 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.
Thanks Partik! 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 |