1044682 – pcp should use systemd

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 1044682 - pcp should use systemd

Summary: pcp should use systemd

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pcp
Sub Component:
Version:	7.0
Hardware:	All
OS:	All
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	---
Assignee:	Nathan Scott
QA Contact:	Miloš Prchlík
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1064025
TreeView+	depends on / blocked

Reported:	2013-12-18 19:44 UTC by jcpunk
Modified:	2019-06-13 07:56 UTC (History)
CC List:	15 users (show)
Fixed In Version:	pcp-3.9.10-4.el7
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2015-03-05 09:40:32 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Bugzilla	996438	0	unspecified	CLOSED	Convert PCP init scripts to systemd	2021-02-22 00:41:40 UTC
Red Hat Product Errata	RHBA-2015:0413	0	normal	SHIPPED_LIVE	pcp bug fix and enhancement update	2015-03-05 14:26:45 UTC

Internal Links: 996438

Description jcpunk 2013-12-18 19:44:10 UTC

Description of problem:pcp uses several legacy init scripts
/etc/rc.d/init.d/pcp
/etc/rc.d/init.d/pmcd
/etc/rc.d/init.d/pmie
/etc/rc.d/init.d/pmlogger
/etc/rc.d/init.d/pmproxy
/etc/rc.d/init.d/pmwebd


Version-Release number of selected component (if applicable):pcp-3.8.6-2.el7.x86_64.rpm


How reproducible:100%


Steps to Reproduce:
1.install pcp
2.look for systemd services
3.find legacy init scripts

Actual results:
legacy init scripts

Expected results:
system unit files with relevant dependencies set

Additional info:

Comment 9 Nathan Scott 2014-02-24 23:11:44 UTC

Quick status update on this one, I'd forgot to make a note here.  An initial investigation was done a little while ago into switching over to native systemd daemon startup mechanisms, rather than the existing init script mechanism.  There are a couple of complications which make this not a straight/simple swap, but I believe they are solvable.

Firstly, two of the init scripts (pmlogger, pmie) do not have a one-script-one-daemon mapping - in a distributed monitoring situation, they may have been configured to start multiple daemons for multiple remote hosts.  I think I know how to tackle this now with systemd, but this had me confused/stumped for awhile.

Second, some of the scripts have before-hand-scripting that needs to be run before the daemon is started - I also was unsure how to tackle this before, but there appears to be multiple options here on closer examination.

These two specific issues aside, the biggest remaining problem is the testsuite.  This contains several hundred tests, many of which make use of the existing init scripts directly.  This will need to be audited, and the scripts modified to conditionally use the systemd daemon startup command variants for platforms like RHEL7 & current Fedora (but not RHEL6 and earlier Fedoras, or the many other platforms PCP supports).

So, there are no blockers to this work going ahead, and go ahead it will - it does have larger scope than one might initially anticipate, however.

Comment 15 Frank Ch. Eigler 2014-09-06 09:55:41 UTC

Note that the degree of systemd support in this release is minimal:
it wraps/hides the old sysvinit scripts as ExecStart/ExecStop oneshot
invocations.  A fuller solution would perhaps:

- have the daemons use stderr/syslog to record trace output into the journal
- invoke the daemons directly rather than through the sysvinit scripts
- use systemd timer units instead of cron jobs
- use unit templates for hard-configured multi-instance daemons (pmlogger, pmie)
- socket activation for pmcd, pmproxy, pmwebd
- add extras like Restart=restart-always for key daemons

Comment 16 Miloš Prchlík 2015-01-07 10:47:21 UTC

Verified for build pcp-3.9.10-8.el7, with regard to degree of support mentioned in comment #15.

Comment 18 errata-xmlrpc 2015-03-05 09:40:32 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://rhn.redhat.com/errata/RHBA-2015-0413.html

Note You need to log in before you can comment on or make changes to this bug.