Sorry for the late response, been really busy lately. What happened was that I
was being stupid and changed some VMs around while Pacemaker/Corosync was
running.When I forced one of the old VMs down, it triggered a failover. The
secondary server didn't have the new VM data/settings yet, so I had to switch
back to the primary. The only problem was when I moved back to the primary
server, it tried to start up one of the old VMs that no longer existed (they
should have existed as far as CRM was concerned), so it was flagged as UNCLEAN.
So, in order to get everything back on track, I need to switch to
maintenance-mode?The secondary server is also running and `crm status` returns
that the primary is UNCLEAN (online) and secondary is online. I've cleaned up
the data/settings for the VMs on both servers to be the same and synced DRBD,
but I'm not sure what I need to do to get the cluster perfect again. Mainly,
like I said before, just get primary clean again and the crm configurat
ion mirrored on both nodes. I have little experience with HA clusters (hence
the rookie mistake noted above) so I'm a bit concerned as to how I can get
everything right without making some stupid mistake again.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
