On fedora 27, pcp 3.12.1 and 3.12.2 pmcds now bind specifically to localhost:XXXX, so they are not reachable from other hosts. (pcp -h localhost works; pcp -h MY_NORMAL_IP_ADDRESS doesn't.) This is a regression for networks that routinely remotely collect pcp data.
Adding -i 0.0.0.0 to /etc/pcp/pmcd/pmcd.options restores the former default.
I realize now this was to some extent deliberate, part of commit 2c721f2444. Nevertheless it creates somewhat of a regression, and is not documented. It would be better if this PMCD_LOCAL=1 change were - conditional on a fresh-install (%install with $1 == 1), - part of the pcp-collector subrpm, and/or - part of the pcp-zeroconf subrpm
Hi, How do you envision complying with fedora packaging guidelines - specifically, as a default enabled service - when installing the base pcp package and adding the 'PMCD_LOCAL=1' change only for? - part of the pcp-collector subrpm, and/or - part of the pcp-zeroconf subrpm
In the meantime I've pushed upstream: commit 8b06e8a16ff4ed0e33a520923f7eb203051cba42 Author: Lukas Berk <lberk> Date: Tue Jan 2 16:11:28 2018 -0500 Only set PM{CD,LOGGER}_LOCAL modes on fc27+ if a fresh install While this change is for fedora packaging guidelines, if the user/admin changes the default values, lets not force this unless it's a fresh install.
Thanks, Luke. My mention of pcp-collector & pcp-zeroconf was to suggest that it is the presence of those subrpms which perhaps should trigger the auto-activation of pmcd & pmlogger (if not pmmgr), I guess as a %post scriptlet, rather than the main pcp subrpm.
pcp-4.0.1-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-67ae01df6c
pcp-4.0.1-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-e0d3cdb266
pcp-4.0.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-a88bef9929
pcp-4.0.1-1.fc28 has been pushed to the Fedora 28 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-2018-67ae01df6c
pcp-4.0.1-1.fc26 has been pushed to the Fedora 26 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-2018-a88bef9929
pcp-4.0.1-1.fc27 has been pushed to the Fedora 27 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-2018-e0d3cdb266
pcp-4.0.1-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
pcp-4.0.1-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
pcp-4.0.1-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.