This issue seems to be similar to BZ #1583159 - "Sample service file vncserver@.service is out of date with systemd changes", which was caused by an update to systemd in response to an upstream issue stating that PID run files should be owned by root, not an unprivileged user (such as 'pcp' in our case). The upstream systemd RFE requesting this is https://github.com/systemd/systemd/issues/6632 and the change that introduced the PID ownership check is https://github.com/systemd/systemd/commit/db256aab13d8a89d583ecd2bacf0aca87c66effc. The change subsequently resulted in a spate of issues with various service daemons unable to start correctly because their PID file was not owned by root (e.g. xinetd and other services, see for example https://github.com/systemd/systemd/issues/8085). As a result, systemd was subsequently updated to not follow symlinks, which apparently circumvented the original issue.
The end result is that /run/PID files should be owned by root and symlinks should not be used. An example of an updated service file to comply with the new systemd is BZ #1583159. So I guess for PCP we're going to need to update the service unit files for all our services to be compatible with the newer versions of systemd. Exactly what changes to make is yet to be determined.
This issue seems to be similar to BZ #1583159 - "Sample service file vncserver@.service is out of date with systemd changes", which was caused by an update to systemd in response to an upstream issue stating that PID run files should be owned by root, not an unprivileged user (such as 'pcp' in our case). The upstream systemd RFE requesting this is https:/ /github. com/systemd/ systemd/ issues/ 6632 and the change that introduced the PID ownership check is https:/ /github. com/systemd/ systemd/ commit/ db256aab13d8a89 d583ecd2bacf0ac a87c66effc. The change subsequently resulted in a spate of issues with various service daemons unable to start correctly because their PID file was not owned by root (e.g. xinetd and other services, see for example https:/ /github. com/systemd/ systemd/ issues/ 8085). As a result, systemd was subsequently updated to not follow symlinks, which apparently circumvented the original issue.
The end result is that /run/PID files should be owned by root and symlinks should not be used. An example of an updated service file to comply with the new systemd is BZ #1583159. So I guess for PCP we're going to need to update the service unit files for all our services to be compatible with the newer versions of systemd. Exactly what changes to make is yet to be determined.