Bug 952977
Summary: | pmstat fails to start | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Marko Myllynen <myllynen> |
Component: | pcp | Assignee: | Nathan Scott <nathans> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | el6 | CC: | fche, mgoodwin, nathans |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-23 03:44:28 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marko Myllynen
2013-04-17 05:51:37 UTC
Hi Marko, I think I know whats caused this - can you confirm that pmcd was not running and that a "service pmcd start" has not been issued on this machine? That file (/var/lib/pcp/pmns/root) should have been created by that process - but thats not done by default anymore. If this is the root cause, we'll probably need to do the namespace rebuild step via rpm rather than via the daemon start script. thanks! Hi Nathan, correct - pmcd was never started on this machine. Thanks. Even with the pmns in place, if pmcd has never been started (or is not running for whatever reason) then pmstat will still fail to run - and so this BZ will not actually be fixed. Perhaps it should revert to pmstat -L if no -h argument was supplied and pmNewContext fails with ECONREFUSED ... ? nevermind, looks liek it already does what I proposed in the previous update : # service pmcd stop Waiting for pmcd to terminate ... # pmstat @ Fri Apr 19 15:13:30 2013 loadavg memory swap io system cpu 1 min swpd free buff cache pi po bi bo in cs us sy id 0.03 0 10231m 210988 1156m 0 0 0 0 60 19 0 0 100 pcp-3.7.2-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/pcp-3.7.2-1.fc19 pcp-3.7.2-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/pcp-3.7.2-1.fc18 pcp-3.7.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/pcp-3.7.2-1.fc17 pcp-3.7.2-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/pcp-3.7.2-1.el6 pcp-3.7.2-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/pcp-3.7.2-1.el5 Package pcp-3.7.2-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pcp-3.7.2-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6095/pcp-3.7.2-1.fc19 then log in and leave karma (feedback). pcp-3.7.2-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. pcp-3.7.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. pcp-3.7.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. pcp-3.7.2-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.7.2-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |