| Summary: | Restart of corosync causes qpidd shutdown | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Pavel Moravec <pmoravec> | ||||
| Component: | qpid-cpp | Assignee: | mick <mgoulish> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | MRG Quality Engineering <mrgqe-bugs> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 2.0 | CC: | jross | ||||
| Target Milestone: | 2.2 | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-11-15 19:46:28 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Sorry, it is not feasible to re-engineer current cluster code to seamlessly survive an openais failure/restart. It *is* possible that a future version of High-Availability Qpid will not require openais at all, but for versions that use openais we will require a qpidd restart after any openais restart. |
Created attachment 502747 [details] qpidd debug log from reproduction Description of problem: Having MRG / qpidd in cluster, a simple restart of openais causes automatic qpidd process shutdown. Version-Release number of selected component (if applicable): any (checked on 1.3 and on 2.0 devel version) How reproducible: 100% Steps to Reproduce: 1. Setup qpidd in cluster 2. service openais start 3. service qpidd start 4. sleep 30 (just to be sure qpidd is fully up) 5. service openais restart 6. service qpidd status Actual results: Step 6 outputs: qpidd dead but pid file exists Expected results: qpidd is robust enough to overcome openais restart Additional info: qpidd debug logs attached, the most relevant part is: .. 2011-06-03 09:49:50 debug Exception constructed: Error in CPG dispatch: library (2) 2011-06-03 09:49:50 critical Error in cluster dispatch: Error in CPG dispatch: library (2) 2011-06-03 09:49:50 notice cluster(10.34.1.222:19533 LEFT) leaving cluster guests 2011-06-03 09:49:50 debug Shutting down CPG 2011-06-03 09:49:50 notice Shut down ..