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 2101574 - [RFE] Provide an environment file for pmlogger farm service default configuration
Summary: [RFE] Provide an environment file for pmlogger farm service default configura...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcp
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.8
Assignee: Nathan Scott
QA Contact: Jan Kurik
Jacob Taylor Valdez
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-27 20:56 UTC by Juan Gamba
Modified: 2023-05-16 08:40 UTC (History)
4 users (show)

Fixed In Version: pcp-5.3.7-9.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-16 08:13:26 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-126392 0 None None None 2022-06-27 21:04:01 UTC
Red Hat Product Errata RHBA-2023:2745 0 None None None 2023-05-16 08:13:33 UTC

Description Juan Gamba 2022-06-27 20:56:19 UTC 
Description of problem:

Request to rename and document the environment file for pmlogger_farm service from /etc/sysconfig/pmlogger_timers to /etc/sysconfig/pmlogger_farm.

Customer considers confusing the naming of pmlogger_farm service environment file, also the same is not documented anywhere. He would expect the settings inside the environment file used for the local instance to work on the farm service.

"The proposal to have a dedicated /etc/sysconfig/pmlogger_farm is a clean and understandable solution. This has also to be documented
At least i would expected to see a comment/header in /etc/sysconfig/pmlogger and the bew /etc/sysconfig/pmlogger_farm in which cases those setting are used and also why it is sepearated in 2 files that can have the same settings."

Version-Release number of selected component (if applicable):

All

How reproducible:

Always

Steps to Reproduce:
1. Setting PMLOGGER_LOCAL=1 on /etc/sysconfig/pmlogger does not apply to pmlogger_farm service.
2.
3.

Actual results:

pmglogger farms service opens serveral ports on external interfaces.

Expected results:

To open ports on the local interface only

Additional info:

Customer applied as a workaround the inclusion of the environmentfile as a drop into the farm service.

"RHEL7 and RHEL8.2,8.4 are also all impacted, but there the same workaround to create /etc/systemd/system/pmlogger.service.d/pmlogger_sysconfig.conf with the 'EnvironmentFile=-/etc/sysconfig/pmlogger' makes it also working that the pmlogger farm is not listening on the external interface anymore"

Regards.,

JGamba
Comment 1 Nathan Scott 2022-06-27 23:22:20 UTC 
Discussing upstream - I think our best option may be to add an /etc/sysconfig/pmlogger_farm configuration file with these settings, but will see what everyone else thinks.  Either way, we do need to resolve this as it remains unclear how to set a default pmlogger sampling interval across a distributed logging farm (/etc/sysconfig/pmlogger is for the primary logger only, according to code and the comment at its head).

Renaming configuration files is unlikely to be the path taken here FWIW, that tends to introduce compatibility problems.

Thanks for raising the issue!
Comment 2 Nathan Scott 2022-06-28 02:13:56 UTC 
I've implemented my preferred approach, started discussion with upstream developers and opened this pull request:
https://github.com/performancecopilot/pcp/pull/1620

... will see how it fares.
Comment 6 errata-xmlrpc 2023-05-16 08:13:26 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 (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-2023:2745
Note You need to log in before you can comment on or make changes to this bug.