Red Hat Bugzilla – Bug 1365658
Several pcp daemons could benefit from auto-restart
Last modified: 2016-10-25 20:58:01 EDT
Created attachment 1189379 [details] implementation for systemd It has been reported that pmwebd sometimes crashes. While the cause(s) are under investigation, this reminds one of other cases where bugs in libpcp or the tools themselves have caused OOM or crashes for pmwebd and pmmgr. In order to protect the user from unnecessary outage of these services, they should be auto-restarted.
+1 - and the same potential benefits exist for pmcd and pmproxy, of course. As discussed here ... http://www.pcp.io/pipermail/pcp/2016-May/010464.html http://www.pcp.io/pipermail/pcp/2016-May/010519.html ... the attached patch is incomplete and needs a little more work. Thanks for opening the BZ though - let's use it as a reminder that a patch like this one, and some QA testing work, is still needed.
(In reply to Nathan Scott from comment #1) > +1 - and the same potential benefits exist for pmcd and pmproxy, of course. Not "of course". Compared to pmwebd & pmmgr, those daemons pose a much smaller load on libpcp and the system, and have been apprx. unaffected by crashes. > As discussed here ... > [...] > ... the attached patch is incomplete and needs a little more work. The patches are complete for pmmgr & pmwebd, the affected daemons.
(In reply to Frank Ch. Eigler from comment #2) > > [...] Compared to pmwebd & pmmgr, those daemons pose a much > smaller load on libpcp and the system, [...] > pmcd and pmproxy can also potentially fail and so could benefit from this treatment, that's all I'm saying. In fact, you said it too... > > The patches are complete for pmmgr & pmwebd, the affected daemons. > Your own attached patch explicitly states that pmcd could benefit, and you are right there. No doubt that was why you attempted to make it work earlier (i.e. before reverting your own changes in that area). Anyway, in the interests of moving things along I have completed this work and it's all been merged upstream (commit b0b6ab0746 for reference).
pcp-3.11.5-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d14b648a5
pcp-3.11.5-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca5c041e73
pcp-3.11.5-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b32e6fdc78
pcp-3.11.5-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-63742f1d5b
pcp-3.11.5-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.5-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.5-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.5-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.