Comment 17 for bug 1850281

(In reply to Brandon J. Wyman from comment #12)
> I am assuming the even newer version that got installed from updates-testing
> should also carry the fix. It does not appear to fix the problem.
>
> [<username>@<host> ~]$ sudo dnf update --enablerepo=updates-testing pcp
> ...
> Oct 24 12:53:46 <host> pmlogger[19176]: Starting pmlogger ...
> Oct 24 12:53:46 <host> systemd[1]: pmlogger.service: Can't open PID file
> /run/pcp/pmlogger.pid (yet?) after start: No such file or directory
...

Brandon, the more serious bug involving incorrect systemd dependencies for the pmlogger service unit is fixed in the pcp-5.0.0 version that is in updates-testing. The less serious (and believed to be benign) issue of systemd complaining about missing pid files and so forth is not fixed, as is explained in https://bugzilla.redhat.com/show_bug.cgi?id=1761962#c2

The systemd complaints also occur for other (non-pcp) services that use type=forking, not just pcp / pmlogger. We will be changing the pcp pmlogger.service config over to type=notify to silence those systemd messages in the near future. I'm currently travelling and unable to commit time until next week at the earliest.

In the mean-time - unless your pmlogger service is actually failing to start, the issues are benign and just systemd being verbose.

Regards