Bug 1991896
| Summary: | Pmlogger processes run in different cgroups | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Flos Qi Guo <qguo> |
| Component: | pcp | Assignee: | pcp-maint <pcp-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Kurik <jkurik> |
| Severity: | medium | Docs Contact: | Apurva Bhide <abhide> |
| Priority: | unspecified | ||
| Version: | 8.4 | CC: | agerstmayr, jkurik, nathans, peter.vreman |
| Target Milestone: | beta | Keywords: | FutureFeature, Triaged |
| Target Release: | 8.6 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pcp-5.3.5-1.el8 | Doc Type: | Release Note |
| Doc Text: |
The PCP pmlogger systemd service now only manages the primary pmlogger instance (localhost) - other pmlogger instances for logging remote hosts are in the pmlogger_farm service. Individual pmlogger instances in a pmlogger farm are best managed with the pmlogctl(1) command. The same change has been made for the pmie service by splitting off the pmie_farm service.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 13:31:13 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
Flos Qi Guo
2021-08-10 11:06:33 UTC
mostly resolved with upstream commit 215bdb10f5831, though a bit more to come yet as mentioned in the commit message:
commit 215bdb10f5831f1164438580811c733ac86177a8
Author: Mark Goodwin <mgoodwin>
Date: Tue Oct 5 11:41:14 2021 +1100
logutil: cleanly separate primary and farm logger services
Cleanly separate primary pmlogger (using pmlogger.service) from
farm pmloggers (using pmlogger_check.service). Further changes
are coming for the pmlogger-farm.service which will manage only
farm loggers (if any). Both the pmlogger and pmlogger-farm
services will need to carefully inherit the same prior service
state in all upgrade and virgin install scenarios.
Also tweak timeouts in pmlogger.service for the local primary
and in pmlogger_check.service for farm loggers.
The KillMode=process setting in pmlogger_check.service is temporary
(will not be needed by pmlogger-farm.service).
Resolves: https://github.com/performancecopilot/pcp/issues/1435
Related BZ#1973833
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 (pcp bug fix and enhancement update), 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-2022:1765 |