On 29 Feb 2012, at 16:33, Florian Haas wrote:
> No, there's an easier way to fix that problem. :)
>
> You said this was a vanilla config that needn't be preserved, right?
> Shut down Corosync on both nodes. Kill the contents of
> /var/lib/heartbeat/crm/. Then bring everything back up.
That worked fine on www5 but not www4, which didn't recreate the cib files.
This time though it did not log any errors, all looks reasonable, but crm
status is still failing to connect, there's still no cib process, and now www5
can't seem to see it either. I tried copying over the cib files from www5
(which seemed to be an empty xml config) but it didn't help: cib still isn't
running.
Also now www5 no longer finds itself - crm status reports 0 nodes.
> That would also be a good opportunity to change your pacemaker service
> configuration from "ver: 0" to "ver: 1" and start pacemakerd ("service
> corosync start; service pacemaker start").
OK, I've done that, but I don't think that's my problem right now! pacemakerd
is running on both nodes.
Marcus
--
Marcus Bointon
Synchromedia Limited: Creators of http://www.smartmessages.net/
UK info@hand CRM solutions
[email protected] | http://www.synchromedia.co.uk/
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
