Comment 3 for bug 1850281

Description of problem:
Everyday, I get these messages:

Jun 17 00:10:13 <host> systemd[1]: pmlogger.service: New main PID 4059499 does not
belong to service, and PID file is not owned by root. Refusing.
Jun 17 00:10:13 <host> systemd[1]: pmlogger.service: New main PID 4059499 does not
belong to service, and PID file is not owned by root. Refusing.
Jun 17 00:11:38 <host> systemd[1]: pmlogger.service: Start operation timed out.
Terminating.
Jun 17 00:11:38 <host> systemd[1]: pmlogger.service: Failed with result 'timeout'.
Jun 17 00:11:38 <host> systemd[1]: Failed to start Performance Metrics Archive Logger.
Jun 17 00:11:46 <host> systemd[1]: pmlogger.service: Supervising process 4066656 which
is not our child. We'll most likely not notice when it exits.

How can I fix the service so that it doesn't give errors every day?

Version-Release number of selected component (if applicable):
pcp-4.3.2-1.fc30.x86_64

How reproducible:
Happens every day.

Steps to Reproduce:
1. No action is required to produce this error. I guess you need to have PCP services enabled and running, though.

Actual results:
errors and warnings

Expected results:
no errors or warnings

Additional info:
PCP data is being collected. I don't really know if there is anything wrong with the data, but I assume it is fine.