Bug 1073658
| Summary: | intermittent pmdasystemd failure at pmcd startup during system boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Frank Ch. Eigler <fche> |
| Component: | pcp | Assignee: | Nathan Scott <nathans> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | fche, kenj, mgoodwin, nathans, pcp, scox |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pcp-3.9.5-1.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-05-30 17:08:23 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
Frank Ch. Eigler
2014-03-06 21:42:15 UTC
Possibly a situation where PM_ERR_PMDANOTREADY might help us? See src/pmdas/rpm/rpm.c::notready() for an example, or pmdasample. cheers. pcpfans.git branch fche/systemd-slow contains commit 82a8aa97, which should fix this problem. I've been unable to reproduce the original problem on a test computer. (Unfortunately, since the problem is intermittent and relies on systemd/journald doing some mysterious concurrent activity, this is not proof that the problem is gone.) Thanks for giving it a spin Frank. If the problem is observed again, it would be really helpful to have the tail of pmcd.log and the pmda's systemd.log files attached to the bug. Ken, certainly will report if/when the problem reappears. Log extracts from the original failures are here at comment #0. There are 2 different timeout scenarios, and I think the connect_pmcd() change will almost certainly fix one of them (the one documented in Comment 0 above). But if the PMDA fails early in life again it will be important to know if this is the _other_ scenario, or my brave assertion is false. Hence the request for the logs if a new failure is observed. pcp-3.9.4-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/pcp-3.9.4-1.fc20 pcp-3.9.4-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/pcp-3.9.4-1.fc19 pcp-3.9.4-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/pcp-3.9.4-1.el6 Package pcp-3.9.4-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing pcp-3.9.4-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1423/pcp-3.9.4-1.el6 then log in and leave karma (feedback). pcp-3.9.4-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. pcp-3.9.5-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/pcp-3.9.5-1.fc19 pcp-3.9.5-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/pcp-3.9.5-1.fc20 pcp-3.9.5-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.9.5-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |