Red Hat Bugzilla – Bug 831722
corosync and pacemaker start should have a delay in between
Last modified: 2014-06-16 02:36:19 EDT
Description of problem:
Sometimes it happens that pcs start spawns both corosync and pacemaker, but pacemaker demands corosync connection before it is actually ready.
This leads to error messages and pacemaker not starting (which is not reported back, which is probably systemd scripts nature ;)).
The error message is this:
r7-node01 pacemakerd: Could not initialize Cluster Configuration Database API instance, error 2
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. pcs start
2. check if pacemaker is up (and no error messages are present as above)
pacemaker not starting, which is silently ignored
The least we can do is to implement delay between corosync start and pacemaker start, hoping for the best outcome.
Better option would be to implement checks of successful start. Maybe it's just systemd improvement that needs to be made, I'm open for suggestions :).
I got to the bottom of this one a few days ago. Our retry logic was borked.
Andrew Beekhof (10 days ago) 7276f67: High: mcp: Correctly retry the connection to corosync on failure
I'll include this in a pacemaker build next week.
Actually, having said that, there are rare occasions when corosync simply fails to start ("service corosync start" fails and corosync is automatically stopped).
Not much pcs or pacemaker can do in that situation though.
Re-assigning to abeekhof for verification since it sounds like this was fixed a few months back in pacemaker.