Comment 6 for bug 1850281

(In reply to Fernando Viñan-Cano from comment #1)
> I can report the same issue, it was happening when my old box was running
> Fedora 29, then when upgraded to Fedora 30 it continued. Now with my brand
> new Fedora 30 machine the issue continues.
>
> SELinux is not reporting any blocks, and then I had this disabled with F29
> so it wasn't that.
>
> What it does effect is the server is unable to store any more than a day of
> performance data. Same version of pcp.

Fernando, can you provide any more details about your system not being able to store more than one day of data? e.g. compressed tarball of your logs below /var/log/pcp/pmlogger and journalctl -b -u pmlogger. If you don't want to attach them to this BZ, could you mail them to me? This might be a separate issue not related to the systemd service issue reported in this BZ because it looks like the pmlogger service is actually being started on subsequent attempts by the PCP scripts, despite all the systemd complaints about the PID files etc.

Thanks